From: Christoph Hellwig <hch@lst.de>
To: Rik van Riel <riel@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Roland McGrath <roland@redhat.com>
Subject: Re: wierd new config options
Date: Thu, 23 Oct 2008 22:19:49 +0200 [thread overview]
Message-ID: <20081023201949.GA29258@lst.de> (raw)
In-Reply-To: <4900D7AE.3010505@redhat.com>
On Thu, Oct 23, 2008 at 03:59:42PM -0400, Rik van Riel wrote:
> Christoph Hellwig wrote:
> >Why is UNEVICTABLE_LRU and option? Is there any rason to turn it off or
> >is this just to confuse users?
>
> Since the swapout code itself is already configurable with
> CONFIG_SWAP, I do believe we want to be able to config out
> the unevictable LRU code.
>
> I guess it could be argued that maybe CONFIG_UNEVICTABLE_LRU
> should just be folded into CONFIG_SWAP...
Sounds like a good plan.
next prev parent reply other threads:[~2008-10-23 20:20 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
2008-10-23 19:26 ` Alexey Dobriyan
2008-10-23 19:59 ` Rik van Riel
2008-10-23 20:19 ` Christoph Hellwig [this message]
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=20081023201949.GA29258@lst.de \
--to=hch@lst.de \
--cc=Lee.Schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--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