[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1156326208.6265.33.camel@Homer.simpson.net>
Date: Wed, 23 Aug 2006 09:43:28 +0000
From: Mike Galbraith <efault@....de>
To: vatsa@...ibm.com
Cc: Ingo Molnar <mingo@...e.hu>, Nick Piggin <nickpiggin@...oo.com.au>,
Sam Vilain <sam@...ain.net>, linux-kernel@...r.kernel.org,
Kirill Korotaev <dev@...nvz.org>,
Balbir Singh <balbir@...ibm.com>, sekharan@...ibm.com,
Andrew Morton <akpm@...l.org>, nagar@...son.ibm.com,
matthltc@...ibm.com, dipankar@...ibm.com
Subject: Re: [PATCH 7/7] CPU controller V1 - (temporary) cpuset interface
On Sun, 2006-08-20 at 23:18 +0530, Srivatsa Vaddagiri wrote:
> As an example, follow these steps to create metered cpusets:
>
>
> # cd /dev
> # mkdir cpuset
> # mount -t cpuset cpuset cpuset
> # cd cpuset
> # mkdir grp_a
> # cd grp_a
> # /bin/echo "6-7" > cpus # assign CPUs 6,7 for this cpuset
> # /bin/echo 0 > mems # assign node 0 for this cpuset
> # /bin/echo 1 > cpu_exclusive
> # /bin/echo 1 > meter_cpu
Implementation might need some idiot proofing.
After mount/cd cpuset, somebody might think "gee, why should I need to
create a group 'all', when it's right there in the root, including all
it's tasks? I'll just set cpu_exclusive, set meter_cpu...
...and after my box finishes rebooting, I'll alert the developer of this
patch set that very bad things happen the instant you do that :)
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists