Linux Container Development
 help / color / mirror / Atom feed
From: Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Robert P. J. Day" <rpjday-L09J2beyid0N/H6P543EQg@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	"menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org"
	<menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] CGROUPS: Group the CGROUPS Kconfig entries to be consecutive.
Date: Wed, 06 Aug 2008 16:50:02 +0530	[thread overview]
Message-ID: <489988E2.70500@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0808060708450.25391-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

Robert P. J. Day wrote:
> On Wed, 6 Aug 2008, KAMEZAWA Hiroyuki wrote:
> 
>> On Mon, 4 Aug 2008 12:16:05 -0400 (EDT)
>> "Robert P. J. Day" <rpjday-L09J2beyid0N/H6P543EQg@public.gmane.org> wrote:
>>
>>> Move a few CGROUPS-related Kconfig entries so that they appear
>>> consecutively when running "make menuconfig."  This shouldn't affect
>>> the functionality.
>>>
>>> Signed-off-by: Robert P. J. Day <rpjday-L09J2beyid0N/H6P543EQg@public.gmane.org>
>>>
>> Seems nice look. (Below is an menuconfig image, I modified a bit for -mm)
>>
>>     lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x
>>   x x    --- Control Group support                                        x x
>>   x x    [ ]   Example debug cgroup subsystem                             x x
>>   x x    [*]   Namespace cgroup subsystem                                 x x
>>   x x    [ ]   Device controller for cgroups                              x x
>>   x x    [*]   Cpuset support                                             x x
>>   x x    [*]   Simple CPU accounting cgroup subsystem                     x x
>>   x x    [*]   Resource counters                                          x x
>>   x x    [*]     Memory Resource Controller for Control Groups            x x
>>   x x    [ ]   Memory resource limit controls for cgroups                 x x
>>
>> How do you think Paul ?
>>
>> Off-topic: to Balbir.
>>
>> How about "Aggregated Memory rlimit controls for cgroup" instead of
>> "Memory resource limit controls for cgroups" ?

Yes, we could do that. We can make it a menu when we add mlock control, etc.

> 
>   ok, i'll leave this with you and you can tweak and apply whatever
> suits you.

I like the way it looks as well.


-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

      parent reply	other threads:[~2008-08-06 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 16:16 [PATCH] CGROUPS: Group the CGROUPS Kconfig entries to be consecutive Robert P. J. Day
     [not found] ` <alpine.LFD.1.10.0808041213540.2600-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-08-06  4:01   ` KAMEZAWA Hiroyuki
     [not found]     ` <20080806130112.82c04664.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2008-08-06 11:10       ` Robert P. J. Day
     [not found]         ` <alpine.LFD.1.10.0808060708450.25391-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-08-06 11:20           ` Balbir Singh [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=489988E2.70500@linux.vnet.ibm.com \
    --to=balbir-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=rpjday-L09J2beyid0N/H6P543EQg@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox