On Tue, Jun 29, 2010 at 5:30 PM, Tommaso Cucinotta < [email protected]> wrote:
> Hello, > > I'm trying to configure statically some basic scheduling parameters > using the /etc/cgconfig.conf file, so that the overall configuration is > automatically done at boot-time. > > Basically, I need to configure such entries as: > cpu.rt_task_period_us > cpu.rt_task_runtime_us > cpu.rt_period_us > cpu.rt_runtime_us > > both in the root group and in a subgroup. However, from the shell I > would need to exec those echo commands in a proper order, otherwise it > fails (I need to configure runtime and period figures for the real-time > multi-processor scheduler [1] developed in the context of IRMOS [2], > just in case anyone is curious, because -- unfortunately -- it uses this > kind of "interface" towards the user-space). > > Ordering is something we don't intentionally focus on in the code, but it does happen today by accident (unless I am misinformed about what we wrote a long time back). What happens is that we add controllers in the order that they appear in cgconfig.conf and write out data in that order. Have you noticed anything to the contrary? > So, my question is: what is the ordering by which cgconfig.conf entries > are processed by cgconfigparser ? Is it fixed ? Is it subject to change > into the future ? Should I drop the use of libcgroup at all for this > kind of settings ? > It is not subject to change. give that you've brought up the requirement, we'll need to make sure we have a really good reason to break it and provide an alternative, if we *ever* do so. Balbir ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Libcg-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libcg-devel
