From: Rik van Riel <riel@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: PERF: performance tests with the split LRU VM in -mm
Date: Mon, 28 Jul 2008 19:57:13 -0400 [thread overview]
Message-ID: <20080728195713.42cbceed@cuia.bos.redhat.com> (raw)
In-Reply-To: <20080728164124.8240eabe.akpm@linux-foundation.org>
On Mon, 28 Jul 2008 16:41:24 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> > Andrew, what is your preference between:
> > http://lkml.org/lkml/2008/7/15/465
> > and
> > http://marc.info/?l=linux-mm&m=121683855132630&w=2
> >
>
> Boy. They both seem rather hacky special-cases. But that doesn't mean
> that they're undesirable hacky special-cases. I guess the second one
> looks a bit more "algorithmic" and a bit less hacky-special-case. But
> it all depends on testing..
I prefer the second one, since it removes the + 1 magic (at least,
for the higher priorities), instead of adding new magic like the
other patch does.
> On a different topic, these:
>
> vmscan-give-referenced-active-and-unmapped-pages-a-second-trip-around-the-lru.patch
> vm-dont-run-touch_buffer-during-buffercache-lookups.patch
>
> have been floating about in -mm for ages, awaiting demonstration that
> they're a net benefit. But all of this new page-reclaim rework was
> built on top of those two patches and incorporates and retains them.
>
> I could toss them out, but that would require some rework and would
> partially invalidate previous testing and who knows, they _might_ be
> good patches. Or they might not be.
>
> What are your thoughts?
I believe you should definately keep those. Being able to better
preserve actively accessed file pages could be a good benefit and
we have yet to discover a downside to those patches.
--
All Rights Reversed
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-07-28 23:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 2:25 Rik van Riel
2008-07-28 14:57 ` Rik van Riel
2008-07-28 15:30 ` Ray Lee
2008-07-28 23:41 ` Andrew Morton
2008-07-28 23:57 ` Rik van Riel [this message]
2008-07-29 0:03 ` Rik van Riel
2008-07-29 0:17 ` Andrew Morton
2008-07-29 0:31 ` Rik van Riel
2008-07-29 0:46 ` Lee Schermerhorn
2008-07-29 13:21 ` Johannes Weiner
2008-07-29 13:28 ` Rik van Riel
2008-07-29 13:04 ` KOSAKI Motohiro
2008-07-29 13:16 ` Rik van Riel
2008-07-29 13:51 ` Johannes Weiner
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=20080728195713.42cbceed@cuia.bos.redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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