public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>
Subject: Re: wierd new config options
Date: Thu, 23 Oct 2008 15:16:44 -0400	[thread overview]
Message-ID: <1224789404.8230.158.camel@lts-notebook> (raw)
In-Reply-To: <20081023181818.GA25430@lst.de>

On Thu, 2008-10-23 at 20:18 +0200, Christoph Hellwig wrote:
> Why is UNEVICTABLE_LRU and option?  Is there any rason to turn it off or
> is this just to confuse users?


We discussed this back when we first submitted the patches.  I
considered the NONRECLAIMABLE/UNEVICTABLE LRU mechanism to be a wee bit
experimental at the time.  I wasn't sure that all platform that do want
memory management would necessarily also want the unevictable lru.  It's
easier for me to build it with the option and remove it later than vice
versa.  If the consensus of the community is that it should always be
enabled, then I'm fine with removing the option.  

Lee

> 
> CORE_DUMP_DEFAULT_ELF_HEADERS is similarly odd, it turns something on
> that break old userspace, this really really should be a sysctl to turn
> on instead of a config option.


  reply	other threads:[~2008-10-23 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 18:18 wierd new config options Christoph Hellwig
2008-10-23 19:16 ` Lee Schermerhorn [this message]
2008-10-23 19:26   ` Alexey Dobriyan
2008-10-23 19:59 ` Rik van Riel
2008-10-23 20:19   ` Christoph Hellwig
2008-11-11 10:26 ` Roland McGrath

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=1224789404.8230.158.camel@lts-notebook \
    --to=lee.schermerhorn@hp.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.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