From: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
To: "Rik van Riel" <riel@redhat.com>
Cc: "Jens Axboe" <jens.axboe@oracle.com>,
"Jean Delvare" <khali@linux-fr.org>,
"Trond Myklebust" <Trond.Myklebust@netapp.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block: Fix LSF default inconsistency
Date: Sat, 13 Dec 2008 00:11:39 +0900 [thread overview]
Message-ID: <2f11576a0812120711l130e07c3x94ff3b1e64959edf@mail.gmail.com> (raw)
In-Reply-To: <49426C16.6040108@redhat.com>
>> Me neither, lets ask the originator of the patch. Rik, why is
>> unevictable lru an option?
>
> I think we had some reasons to keep it as a separate config
> option during development, but nowadays we might as well
> put it all just under CONFIG_SWAP...
I'm sad ;)
To move mlocked file cache page to unevictable list is useful although
swapless embedded device.
Actually, number of scanning pages of reclaim is calculated by number
of pages in list.
if unevictable page stay in evictable list a lot, reclaim logic can
calculate wrong scanning number.
next prev parent reply other threads:[~2008-12-12 15:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 10:16 Jean Delvare
2008-12-11 10:41 ` Jens Axboe
2008-12-11 10:58 ` Jean Delvare
2008-12-11 11:08 ` Jens Axboe
2008-12-11 11:33 ` KOSAKI Motohiro
2008-12-11 11:36 ` Jens Axboe
2008-12-11 11:44 ` KOSAKI Motohiro
2008-12-12 7:58 ` Jens Axboe
2008-12-12 13:50 ` Rik van Riel
2008-12-12 15:11 ` KOSAKI Motohiro [this message]
2008-12-12 16:01 ` Hugh Dickins
2008-12-12 16:35 ` Rik van Riel
2008-12-12 17:37 ` Hugh Dickins
2008-12-12 18:00 ` Rik van Riel
2008-12-12 19:26 ` Hugh Dickins
2008-12-11 12:44 ` Jean Delvare
2008-12-11 12:50 ` Jens Axboe
2008-12-12 7:48 ` Jean Delvare
2008-12-12 7:54 ` Jens Axboe
2008-12-12 9:41 ` Jean Delvare
2008-12-12 18:18 ` Jens Axboe
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=2f11576a0812120711l130e07c3x94ff3b1e64959edf@mail.gmail.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=Trond.Myklebust@netapp.com \
--cc=jens.axboe@oracle.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@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
all inboxes | Powered by JetHome®