From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Andrew Morton <akpm@osdl.org>
Cc: nickpiggin@yahoo.com.au, nikita@clusterfs.com,
Linux-Kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH]: 1/4 batch mark_page_accessed()
Date: Tue, 30 Nov 2004 20:57:07 -0200 [thread overview]
Message-ID: <20041130225707.GA2315@dmt.cyclades> (raw)
In-Reply-To: <20041130173323.0b3ac83d.akpm@osdl.org>
On Tue, Nov 30, 2004 at 05:33:23PM -0800, Andrew Morton wrote:
> Marcelo Tosatti <marcelo.tosatti@cyclades.com> wrote:
> >
> > Because the ordering of LRU pages should be enhanced in respect to locality,
> > with the mark_page_accessed batching you group together tasks accessed pages
> > and move them at once to the active list.
> >
> > You maintain better locality ordering, while decreasing the precision of aging/
> > temporal locality.
> >
> > Which should enhance disk writeout performance.
>
> I'll buy that explanation. Although I'm a bit sceptical that it is
> measurable.
Its just a theory that makes sense to me, but yes we need to be measure it.
> Was that particular workload actually performing significant amounts of
> writeout in vmscan.c? (We should have direct+kswapd counters for that, but
> we don't. /proc/vmstat:pgrotated will give us an idea).
I strongly believe so, its a memory hungry benchmark - I'll collect status later
on this week or the next.
> > On the other hand, without batching you mix the locality up in LRU - the LRU becomes
> > more precise in terms of "LRU aging", but less ordered in terms of sequential
> > access pattern.
> >
> > The disk IO intensive reaim has very significant gain from the batching, its
> > probably due to the enhanced LRU ordering (what Nikita says).
> >
> > The slowdown is probably due to the additional atomic_inc by page_cache_get().
> >
> > Is there no way to avoid such page_cache_get there (and in lru_cache_add also)?
>
> Not really. The page is only in the pagevec at that time - if someone does
> a put_page() on it the page will be freed for real, and will then be
> spilled onto the LRU. Messy.
We could handle such situation on allocation and during vmscan - maybe its doable.
Just pondering, maybe its indeed too messy to even ponder about.
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-11-30 22:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 15:44 Nikita Danilov
2004-11-21 21:12 ` Andrew Morton
2004-11-24 10:40 ` Marcelo Tosatti
2004-11-24 16:32 ` Marcelo Tosatti
2004-11-24 21:53 ` Nikita Danilov
2004-11-26 18:58 ` Marcelo Tosatti
2004-11-27 0:37 ` Nick Piggin
2004-11-30 16:29 ` Marcelo Tosatti
2004-12-01 1:33 ` Andrew Morton
2004-11-30 22:57 ` Marcelo Tosatti [this message]
2004-12-01 12:23 ` Nikita Danilov
2004-12-01 18:58 ` Marcelo Tosatti
2004-12-02 1:59 ` Andrew Morton
2004-11-27 10:41 ` Nikita Danilov
2004-11-27 8:19 ` Marcelo Tosatti
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=20041130225707.GA2315@dmt.cyclades \
--to=marcelo.tosatti@cyclades.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=nikita@clusterfs.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