From: Andi Kleen <andi@firstfloor.org>
To: Rik van Riel <riel@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
hugh@veritas.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, npiggin@suse.de, mztabzr@0pointer.de,
mpm@selenic.com
Subject: Re: [PATCH] mm: MADV_WILLNEED implementation for anonymous memory
Date: Thu, 31 Jan 2008 12:32:24 +0100 [thread overview]
Message-ID: <20080131113224.GB31090@one.firstfloor.org> (raw)
In-Reply-To: <20080131055209.6adede04@riellaptop.surriel.com>
On Thu, Jan 31, 2008 at 05:52:09AM -0500, Rik van Riel wrote:
> On Thu, 31 Jan 2008 12:06:10 +0100
> Andi Kleen <andi@firstfloor.org> wrote:
>
> > > Yeah, the 2.5 switch to physical scanning killed us there.
> > >
> > > I still don't know why my
> > > allocate-swapspace-according-to-virtual-address change didn't
> > > help. Much. Marcelo played with that a bit too.
> >
> > I've been thinking about just always doing swap on > page clusters.
> > Any reason swapping couldn't be done on e.g. 1MB chunks?
>
> Don't malloc() and free() hopelessly fragment memory
> over time, ensuring that little related data can be
> found inside each 1MB chunk if the process is large
> enough? (say, firefox)
Even if they do (I don't know if it's true or not) it does not really
matter because on modern hard disks/systems it does not cost less to
transfer 1MB versus 4K. The actual threshold seems to be rising in fact.
The only drawback is that the swap might be full sooner, but
I would actually consider this a feature because it would likely
end many prolonged oom death dances much sooner.
-Andi
--
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-01-31 11:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 17:28 [PATCH] mm: MADV_WILLNEED implementation for anonymous memory, mm: MADV_WILLNEED implementation for anonymous memory Peter Zijlstra
2008-01-30 18:15 ` [PATCH] " Matt Mackall
2008-01-30 22:40 ` Andrew Morton
2008-01-31 8:44 ` Peter Zijlstra
2008-01-31 9:12 ` Andrew Morton
2008-01-31 9:35 ` Peter Zijlstra
2008-01-31 9:47 ` Andrew Morton
2008-01-31 9:53 ` Peter Zijlstra
2008-01-31 10:05 ` Andrew Morton
2008-01-31 10:10 ` Peter Zijlstra
2008-01-31 10:18 ` Andrew Morton
2008-01-31 10:15 ` Andi Kleen
2008-01-31 10:19 ` Andrew Morton
2008-01-31 11:06 ` Andi Kleen
2008-01-31 10:52 ` Rik van Riel
2008-01-31 11:32 ` Andi Kleen [this message]
2008-01-31 11:09 ` 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=20080131113224.GB31090@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=mztabzr@0pointer.de \
--cc=npiggin@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).