mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <jj@chaosbits.net>
To: Michal Hocko <mhocko@suse.cz>
Cc: Jiri Kosina <trivial@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation/vm/unevictable-lru.txt: CONFIG_UNEVICTABLE_LRU doesn't exist anymore
Date: Thu, 17 Mar 2011 00:55:33 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.00.1103170051510.24706@swampdragon.chaosbits.net> (raw)
In-Reply-To: <20110316140137.GA12544@tiehlicka.suse.cz>

On Wed, 16 Mar 2011, Michal Hocko wrote:

> commit 6837765963f1723e80ca97b1fae660f3a60d77df has removed the config
> option so we should sync up the doc as well.
> 
> Signed-off-by: Michal Hocko <mhocko@suse.cz>
> ---
>  Documentation/vm/unevictable-lru.txt |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/vm/unevictable-lru.txt b/Documentation/vm/unevictable-lru.txt
> index 2d70d0d..aad6607 100644
> --- a/Documentation/vm/unevictable-lru.txt
> +++ b/Documentation/vm/unevictable-lru.txt
> @@ -84,8 +84,7 @@ indicate that the page is being managed on the unevictable list.
>  
>  The PG_unevictable flag is analogous to, and mutually exclusive with, the
>  PG_active flag in that it indicates on which LRU list a page resides when
> -PG_lru is set.  The unevictable list is compile-time configurable based on the
> -UNEVICTABLE_LRU Kconfig option.
> +PG_lru is set. 
>  
>  The Unevictable LRU infrastructure maintains unevictable pages on an additional
>  LRU list for a few reasons:
> 

Reviewed-by: Jesper Juhl <jj@chaosbits.net>


-- 
Jesper Juhl <jj@chaosbits.net>            http://www.chaosbits.net/
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please.


      parent reply	other threads:[~2011-03-16 23:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 14:01 Michal Hocko
2011-03-16 23:37 ` Jiri Kosina
2011-03-16 23:55 ` Jesper Juhl [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=alpine.LNX.2.00.1103170051510.24706@swampdragon.chaosbits.net \
    --to=jj@chaosbits.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=trivial@kernel.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

all inboxes | Powered by JetHome®