linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: David Rientjes <rientjes@google.com>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	mingo@elte.hu, david.woodhouse@intel.com, gregkh@suse.de,
	davem@davemloft.net, axboe@kernel.dk, holt@sgi.com,
	linux-arch@vger.kernel.org, linux@arm.linux.org.uk,
	hskinnemoen@gmail.com, egtvedt@samfundet.no, msalter@redhat.com,
	a-jacquiot@ti.com, starvik@axis.com, jesper.nilsson@axis.com,
	dhowells@redhat.com, takata@linux-m32r.org, geert@linux-m68k.org,
	yasutake.koichi@jp.panasonic.com, jonas@southpole.se,
	kyle@mcmartin.ca, deller@gmx.de, jejb@parisc-linux.org,
	chris@zankel.net, greg@kroah.com, davej@redhat.com,
	airlied@linux.ie, jkosina@suse.cz, mchehab@infradead.org,
	johannes@sipsolutions.net, linville@tuxdriver.com
Subject: Re: [PATCH] kconfig: untangle EXPERT and EMBEDDED
Date: Thu, 12 Jan 2012 11:18:06 +0100	[thread overview]
Message-ID: <20120112101805.GA2375@turtle.usersys.redhat.com> (raw)
In-Reply-To: <201201120918.53026.arnd@arndb.de>

On Thu, Jan 12, 2012 at 09:18:52AM +0000, Arnd Bergmann wrote:
> On Wednesday 11 January 2012, David Rientjes wrote:
> > We discussed this when the patch was made to change EMBEDDED to EXPERT and 
> > we knew that things like CONFIG_SLOB exist that would only make sense on a 
> > platform with a very small memory footprint.  So what criteria are you 
> > using to determine what makes sense for EMBEDDED or not and what would be 
> > generally useful for platforms with very small memory footprints?
> > 
> > I would think that something like CONFIG_SMALLMEM would identify those 
> > candidates (for things like SLOB) and then you could separate the rest 
> > based on the platform they exist for since you're essentially introducing 
> > a new config symbol here that existed in the past but are now using it 
> > with different semantics.

No, I'm putting EMBEDDED back to work doing the same thing it did before,
i.e. the semantics for it are the same as they were before 6a108a14fa35.
This is not a revert of that patch though. I'm keeping EXPERT, but
ensuring it doesn't do everything EMBEDDED used to do. I'm ensuring it
only does what it advertises it does, which is to give a useful configmenu
cleanup symbol to the whole kernel.

> 
> The CONFIG_SMALLMEM would also require people to know what they are doing,
> beyond what we expect the average person building a kernel to, which is
> just what CONFIG_EXPERT means, and the same reason why we ended up renaming
> CONFIG_EMBEDDED to CONFIG_EXPERT. People have a very different understanding
> of what "embedded" actually means, and not all of those require small
> memory footprint or even a custom kernel. Let's just stay with CONFIG_EXPERT.

For the SLOB example, and everything else that is 'if EXPERT' after
6a108a14fa35, then don't worry, they are still 'if EXPERT'. See the patch.

I chose EMBEDDED to handle the side effects, simply because it used to
anyway. I think it's best that I leave any further customizing, such as
replacing EMBEDDED with SMALLMEM for particular options, to those that are
more familiar with those options. I can conceive of people wanting EXPERT
-> SMALLMEM -> SLOB type menus, but that's not in the scope of this patch.

Drew

  reply	other threads:[~2012-01-12 11:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 15:16 [PATCH] kconfig: untangle EXPERT and EMBEDDED Andrew Jones
2012-01-11 21:57 ` David Rientjes
2012-01-12  9:18   ` Arnd Bergmann
2012-01-12 10:18     ` Andrew Jones [this message]
2012-01-12 21:06       ` David Rientjes
2012-01-13  8:51         ` Andrew Jones
2012-01-13 10:53           ` David Rientjes
2012-01-13 12:22             ` Andrew Jones
2012-01-13 21:27               ` David Rientjes
2012-01-16  9:20                 ` Andrew Jones
2012-01-16 23:28                   ` David Rientjes
2012-01-17 14:27                     ` Andrew Jones
2012-01-17 20:46                       ` David Rientjes
2012-01-18  8:14                         ` Andrew Jones
2012-01-18  9:19                           ` David Rientjes
2012-01-16 15:31                 ` Jerome Marchand
2012-01-16 23:37                   ` David Rientjes
2012-01-17 14:46                     ` Andrew Jones
2012-01-17 20:54                       ` David Rientjes
2012-01-18  8:51                         ` Jerome Marchand
2012-01-18  8:56                         ` Andrew Jones
2012-01-18  9:31                           ` David Rientjes
2012-01-18  9:54                             ` Andrew Jones
2012-01-18  9:38                         ` Andrew Jones
2012-01-12 20:59     ` David Rientjes
2012-01-16 15:40 ` Jerome Marchand
2012-01-16 15:50   ` Andrew Jones
2012-01-16 17:34     ` Geert Uytterhoeven
2012-01-17  8:28       ` Andrew Jones
2012-01-18 11:08 ` Andrew Jones
2012-01-18 20:28   ` Andrew Morton
2012-01-18 20:46     ` Russell King - ARM Linux
2012-01-18 21:04     ` Alexey Dobriyan
2012-01-18 21:36       ` Andrew Morton
2012-01-18 21:48     ` Paul Bolle
2012-01-18 21:55       ` Andrew Morton
2012-01-18 22:13         ` Russell King - ARM Linux
2012-01-18 22:06       ` Alexey Dobriyan
2012-01-18 22:13       ` Dave Jones
2012-01-19  8:09     ` Andrew Jones
2012-01-23 13:46     ` Andrew Jones
2012-01-24  0:43       ` David Rientjes

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=20120112101805.GA2375@turtle.usersys.redhat.com \
    --to=drjones@redhat.com \
    --cc=a-jacquiot@ti.com \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=axboe@kernel.dk \
    --cc=chris@zankel.net \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --cc=david.woodhouse@intel.com \
    --cc=deller@gmx.de \
    --cc=dhowells@redhat.com \
    --cc=egtvedt@samfundet.no \
    --cc=geert@linux-m68k.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=holt@sgi.com \
    --cc=hskinnemoen@gmail.com \
    --cc=jejb@parisc-linux.org \
    --cc=jesper.nilsson@axis.com \
    --cc=jkosina@suse.cz \
    --cc=johannes@sipsolutions.net \
    --cc=jonas@southpole.se \
    --cc=kyle@mcmartin.ca \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=linville@tuxdriver.com \
    --cc=mchehab@infradead.org \
    --cc=mingo@elte.hu \
    --cc=msalter@redhat.com \
    --cc=rientjes@google.com \
    --cc=starvik@axis.com \
    --cc=takata@linux-m32r.org \
    --cc=yasutake.koichi@jp.panasonic.com \
    /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;
as well as URLs for NNTP newsgroup(s).