From: Rik van Riel <riel@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Hugh Dickins <hugh@veritas.com>, Ken Chen <kenchen@google.com>,
linux-mm@kvack.org
Subject: Re: [patch] not to disturb page LRU state when unmapping memory range
Date: Wed, 31 Jan 2007 22:21:15 -0500 [thread overview]
Message-ID: <45C15CAB.2090607@redhat.com> (raw)
In-Reply-To: <20070131144855.8fe255ff.akpm@osdl.org>
Andrew Morton wrote:
> Perhaps we're approaching this from the wrong direction. Rather than
> looking at the code and saying "hey, we should change that", we should be
> looking at workloads and seeing how they can be improved. Perhaps.
I think this makes a lot of sense. It may not be benchmarkable,
because there is no exhaustive test of workloads, but we can at
least come up with several conceptual groups of workloads that
should be kept in mind when changing things to the VM.
I could think of a few workloads and their characteristics and
desired behaviour:
1) desktop workload - program working sets need to be kept in
memory and protected from pressure by streaming IO
2) database workload - some pages get accessed more frequently
than others, those need to be kept resident in memory
3) file server workload - some pages get accessed more frequently
than others, those need to be kept resident in memory. This
is similar to the database workload, except the inter-reference
distance on a file server is WAY larger and an LRU queue is
likely not large enough to catch even the frequently accessed
pages.
4) web server workload - somewhere in-between the desktop and the
file server, the working sets of the server programs need to be
kept in memory, and we want to cache the frequently accessed
data pages
5) developer desktop - like the desktop workload, except we have
programs like git and rsync doing streaming IO with double
accesses next to each other, which will push the working sets
of the desktop programs out of memory if our use-once algorithm
gets fooled
6) realtime data processing - this kind of workload is usually
mlocked, but sometimes still wants to do lots of file IO.
We need to make sure the VM does not get upset by the sometimes
large amount of mlocked data
7) ... fill in your own workload here :)
--
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is. Each group
calls the other unpatriotic.
--
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:[~2007-02-01 3:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 4:41 Ken Chen
2007-01-31 12:26 ` Peter Zijlstra
2007-01-31 19:15 ` Balbir Singh
2007-01-31 19:30 ` Christoph Lameter
2007-01-31 18:02 ` Hugh Dickins
2007-01-31 21:43 ` Peter Zijlstra
2007-01-31 21:51 ` Ken Chen
2007-01-31 22:04 ` Andrew Morton
2007-01-31 22:25 ` Peter Zijlstra
2007-01-31 22:48 ` Andrew Morton
2007-01-31 23:52 ` Peter Zijlstra
2007-02-01 0:33 ` Andrew Morton
2007-02-01 3:21 ` Rik van Riel [this message]
2007-02-01 3:13 ` Rik van Riel
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=45C15CAB.2090607@redhat.com \
--to=riel@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=kenchen@google.com \
--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