On 10/30/06, Paul Jackson <[email protected]> wrote:
You mean let the system admin, say, of a system determine whether or not CKRM/RG and cpusets have one shared, or two separate, hierarchies?
Yes - let the sysadmin define the process groupings, and how those groupings get associated with resource control entities. The default should be that all the hierarchies are the same, since I think that's likely to be the common case. Paul - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices
- From: Paul Jackson <[email protected]>
- Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices
- References:
- [RFC] Resource Management - Infrastructure choices
- From: Srivatsa Vaddagiri <[email protected]>
- Re: [RFC] Resource Management - Infrastructure choices
- From: "Paul Menage" <[email protected]>
- Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices
- From: Paul Jackson <[email protected]>
- Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices
- From: "Paul Menage" <[email protected]>
- Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices
- From: Paul Jackson <[email protected]>
- [RFC] Resource Management - Infrastructure choices
- Prev by Date: Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- Next by Date: Re: 2.6.19-rc3: known unfixed regressions (v3)
- Previous by thread: Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices
- Next by thread: Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices
- Index(es):