|
|
| (26 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| {{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}
| | #REDIRECT[[:Features/ControlGroups]] |
| | |
| <!-- All fields on this form are required to be accepted by FESCo.
| |
| We also request that you maintain the same order of sections so that all of the feature pages are uniform. -->
| |
| | |
| <!-- The actual name of your feature page should look something like: Features/ResourceMgt. This keeps all features in the same namespace -->
| |
| | |
| = Feature Name =
| |
| Resource Management
| |
| | |
| == Summary ==
| |
| <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. -->
| |
| Resource Management is an upstream feature that allows system resources to be partitioned/divided up amongst different processes, or a group of processes.
| |
| | |
| == Owner ==
| |
| <!--This should link to your home wiki page so we know who you are-->
| |
| * Name: lwang
| |
| | |
| <!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved-->
| |
| * email: lwang@redhat.com
| |
| | |
| == Current status ==
| |
| * Targeted release: [[Releases/{{FedoraVersion||next}} | {{FedoraVersion|long|next}} ]]
| |
| * Last updated: (DATE)
| |
| * Percentage of completion: XX%
| |
| | |
| <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
| |
| | |
| == Detailed Description ==
| |
| Resource Management/Control Groups
| |
| | |
| Control Groups provide a mechanism for aggregating/partitioning sets of
| |
| tasks, and all their future children, into hierarchical groups with
| |
| specialized behaviour.
| |
| | |
| Definitions:
| |
|
| |
| A *cgroup* associates a set of tasks with a set of parameters for one
| |
| or more subsystems.
| |
|
| |
| A *subsystem* is a module that makes use of the task grouping
| |
| facilities provided by cgroups to treat groups of tasks in
| |
| particular ways. A subsystem is typically a "resource controller" that
| |
| schedules a resource or applies per-cgroup limits, but it may be
| |
| anything that wants to act on a group of processes, e.g. a
| |
| virtualization subsystem.
| |
|
| |
| A *hierarchy* is a set of cgroups arranged in a tree, such that
| |
| every task in the system is in exactly one of the cgroups in the
| |
| hierarchy, and a set of subsystems; each subsystem has system-specific
| |
| state attached to each cgroup in the hierarchy. Each hierarchy has
| |
| an instance of the cgroup virtual filesystem associated with it.
| |
|
| |
| At any one time there may be multiple active hierachies of task
| |
| cgroups. Each hierarchy is a partition of all tasks in the system.
| |
|
| |
| User level code may create and destroy cgroups by name in an
| |
| instance of the cgroup virtual file system, specify and query to
| |
| which cgroup a task is assigned, and list the task pids assigned to
| |
| a cgroup. Those creations and assignments only affect the hierarchy
| |
| associated with that instance of the cgroup file system.
| |
|
| |
| On their own, the only use for cgroups is for simple job
| |
| tracking. The intention is that other subsystems hook into the generic
| |
| cgroup support to provide new attributes for cgroups, such as
| |
| accounting/limiting the resources which processes in a cgroup can
| |
| access. For example, cpusets (see Documentation/cpusets.txt) allows
| |
| you to associate a set of CPUs and a set of memory nodes with the
| |
| tasks in each cgroup.
| |
| | |
| == Benefit to Fedora ==
| |
| <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
| |
| | |
| == Scope ==
| |
| There are several sub-features under control group:
| |
| | |
| * CPUSET
| |
| | |
| * CPUACCT
| |
| | |
| * MEMCTL
| |
| | |
| * NETCTL
| |
| | |
| * IOCTL
| |
| | |
| == How To Test ==
| |
| <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.
| |
| | |
| Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
| |
| | |
| A good "how to test" should answer these four questions:
| |
| | |
| 0. What special hardware / data / etc. is needed (if any)?
| |
| 1. How do I prepare my system to test this feature? What packages
| |
| need to be installed, config files edited, etc.?
| |
| 2. What specific actions do I perform to check that the feature is
| |
| working like it's supposed to?
| |
| 3. What are the expected results of those actions?
| |
| | |
| -->
| |
| | |
| == User Experience ==
| |
| <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. -->
| |
| | |
| == Dependencies ==
| |
| <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? -->
| |
| | |
| == Contingency Plan ==
| |
| <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->
| |
| | |
| == Documentation ==
| |
| <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. -->
| |
| | |
| | |
| == Release Notes ==
| |
| | |
| <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
| |
| <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
| |
| | |
| == Comments and Discussion ==
| |
| | |
| * See [[Talk:Features/YourFeatureName]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
| |
| | |
| | |
| ----
| |
| | |
| [[Category:FeaturePageIncomplete]]
| |
| <!-- When your feature page is completed and ready for review -->
| |
| <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
| |
| <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
| |
| <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
| |
