All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: KOSAKI Motohiro <m-kosaki@ceres.dti.ne.jp>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	John Stoffel <john@stoffel.org>, Andi Kleen <andi@firstfloor.org>,
	akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] Document huge memory/cache overhead of memory controller in Kconfig
Date: Fri, 22 Feb 2008 00:55:27 +0100	[thread overview]
Message-ID: <20080221235527.GD25977@elf.ucw.cz> (raw)
In-Reply-To: <2f11576a0802210646u77409690me940717fac746315@mail.gmail.com>

Hi!

> >  > >> For ordinary desktop people, memory controller is what developers
> >  > >> know as MMU or sometimes even some other mysterious piece of silicon
> >  > >> inside the heavy box.
> >  > >
> >  > >Actually I'd guess 'memory controller' == 'DRAM controller' == part of
> >  > >northbridge that talks to DRAM.
> >  >
> >  > Yeah that must have been it when Windows says it found a new controller
> >  > after changing the mainboard underneath.
> >
> >  Just for fun... this option really has to be renamed:
> 
> I think one reason of many people easy confusion is caused by bad menu
> hierarchy.
> I popose mem-cgroup move to child of cgroup and resource counter
> (= obey denend on).

> +config CGROUP_MEM_CONT
> +	bool "Memory controller for cgroups"

Memory _resource_ controller for cgroups?

> +	depends on CGROUPS && RESOURCE_COUNTERS
> +	help
> +	  Provides a memory controller that manages both page cache and

Same here.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: KOSAKI Motohiro <m-kosaki@ceres.dti.ne.jp>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	John Stoffel <john@stoffel.org>, Andi Kleen <andi@firstfloor.org>,
	akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] Document huge memory/cache overhead of memory controller in Kconfig
Date: Fri, 22 Feb 2008 00:55:27 +0100	[thread overview]
Message-ID: <20080221235527.GD25977@elf.ucw.cz> (raw)
In-Reply-To: <2f11576a0802210646u77409690me940717fac746315@mail.gmail.com>

Hi!

> >  > >> For ordinary desktop people, memory controller is what developers
> >  > >> know as MMU or sometimes even some other mysterious piece of silicon
> >  > >> inside the heavy box.
> >  > >
> >  > >Actually I'd guess 'memory controller' == 'DRAM controller' == part of
> >  > >northbridge that talks to DRAM.
> >  >
> >  > Yeah that must have been it when Windows says it found a new controller
> >  > after changing the mainboard underneath.
> >
> >  Just for fun... this option really has to be renamed:
> 
> I think one reason of many people easy confusion is caused by bad menu
> hierarchy.
> I popose mem-cgroup move to child of cgroup and resource counter
> (= obey denend on).

> +config CGROUP_MEM_CONT
> +	bool "Memory controller for cgroups"

Memory _resource_ controller for cgroups?

> +	depends on CGROUPS && RESOURCE_COUNTERS
> +	help
> +	  Provides a memory controller that manages both page cache and

Same here.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2008-02-21 23:55 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 12:23 [PATCH] Document huge memory/cache overhead of memory controller in Kconfig Andi Kleen
2008-02-20 12:23 ` Andi Kleen
2008-02-20 12:52 ` Balbir Singh
2008-02-20 12:52   ` Balbir Singh
2008-02-20 15:00   ` John Stoffel
2008-02-20 15:00     ` John Stoffel
2008-02-20 15:20     ` Balbir Singh
2008-02-20 15:20       ` Balbir Singh
2008-02-20 15:49       ` Jan Engelhardt
2008-02-20 15:49         ` Jan Engelhardt
2008-02-20 16:10         ` John Stoffel
2008-02-20 16:10           ` John Stoffel
2008-02-20 16:15           ` Balbir Singh
2008-02-20 16:15             ` Balbir Singh
2008-02-20 17:00             ` Andi Kleen
2008-02-20 17:00               ` Andi Kleen
2008-02-21  6:49             ` KAMEZAWA Hiroyuki
2008-02-21  6:49               ` KAMEZAWA Hiroyuki
2008-02-21  6:52               ` Balbir Singh
2008-02-21  6:52                 ` Balbir Singh
2008-02-20 18:19         ` Pavel Machek
2008-02-20 18:19           ` Pavel Machek
2008-02-20 18:28           ` Jan Engelhardt
2008-02-20 18:28             ` Jan Engelhardt
2008-02-20 18:51             ` Pavel Machek
2008-02-20 18:51               ` Pavel Machek
2008-02-21 14:46               ` KOSAKI Motohiro
2008-02-21 14:46                 ` KOSAKI Motohiro
2008-02-21 14:52                 ` Balbir Singh
2008-02-21 14:52                   ` Balbir Singh
2008-02-21 23:55                 ` Pavel Machek [this message]
2008-02-21 23:55                   ` Pavel Machek
2008-02-22  3:09                   ` KOSAKI Motohiro
2008-02-22  3:09                     ` KOSAKI Motohiro
2008-02-20 16:15       ` John Stoffel
2008-02-20 16:15         ` John Stoffel
2008-02-20 16:54       ` Ray Lee
2008-02-20 16:54         ` Ray Lee
2008-02-20 16:57     ` Andi Kleen
2008-02-20 16:57       ` Andi Kleen
2008-02-21  4:35   ` Nick Piggin
2008-02-21  4:35     ` Nick Piggin
2008-02-21  5:06     ` Balbir Singh
2008-02-21  5:06       ` Balbir Singh
     [not found]       ` <200802211622.51751.nickpiggin@yahoo.com.au>
2008-02-21  5:46         ` Balbir Singh
2008-02-21  5:46           ` Balbir Singh
2008-02-21 10:44       ` Andi Kleen
2008-02-21 10:44         ` Andi Kleen
2008-02-22  4:41         ` Balbir Singh
2008-02-22  4:41           ` Balbir Singh
2008-02-22  9:51           ` Andi Kleen
2008-02-22  9:51             ` Andi Kleen
2008-02-22 12:14             ` Balbir Singh
2008-02-22 12:14               ` Balbir Singh
2008-02-22 13:00               ` Andi Kleen
2008-02-22 13:00                 ` Andi Kleen
2008-02-22 15:47                 ` Balbir Singh
2008-02-22 15:47                   ` Balbir Singh
2008-02-21 10:37     ` Andi Kleen
2008-02-21 10:37       ` Andi Kleen
2008-02-21 11:03       ` Balbir Singh
2008-02-21 11:03         ` Balbir Singh
2008-02-22  6:59         ` KAMEZAWA Hiroyuki
2008-02-22  6:59           ` KAMEZAWA Hiroyuki
2008-02-22  7:06           ` Balbir Singh
2008-02-22  7:06             ` Balbir Singh

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=20080221235527.GD25977@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=andi@firstfloor.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=jengelh@computergmbh.de \
    --cc=john@stoffel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m-kosaki@ceres.dti.ne.jp \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.