public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Benchmarking objrmap under memory pressure
Date: Thu, 15 Apr 2004 16:08:51 +0200	[thread overview]
Message-ID: <20040415140851.GF2150@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0404151439140.8774-100000@localhost.localdomain>

On Thu, Apr 15, 2004 at 02:45:21PM +0100, Hugh Dickins wrote:
> I like file vma merging, but I am puzzled why we (you) bothered 
> to implement anon vma merging before and not file vma merging,
> if the file vma merging is so much more important.  I suppose
> it's something you learnt later, or the apps evolved.

both things, I learnt it later, but it's also because the anon-vma
pretty much "forced" me not to be lazy about the inodes ;). It's
something I planned already when I changed the mmap mering to handle
inodes too  and submitted to Andrew that merged it in 2.5 mainline, the
only reason I didn't do it at that time, is that it was originally
developed for 2.4, and the less changes the better, so at that time I
only fixed the showstopper inode-merging for mmap and not mprotect.

At 2.4 time I also planned eventually to add the vma merging to mlock
but it didn't happen yet ;).

> Indeed.  If anonmm does live on, I would want to add the file
> vma merging; but when things (mpol, prio_tree, i_shared locking)
> have settled down rather than now - we've lived without it for
> some years, can live without it for a few weeks more.

Sure.

  reply	other threads:[~2004-04-15 14:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13  7:39 Benchmarking objrmap under memory pressure Martin J. Bligh
2004-04-13  7:51 ` Andrew Morton
2004-04-13  7:55   ` Martin J. Bligh
2004-04-13 21:59   ` Andrea Arcangeli
2004-04-14  0:38   ` Martin J. Bligh
2004-04-14 16:27     ` Andrea Arcangeli
2004-04-14 16:42       ` Martin J. Bligh
2004-04-14 17:11         ` Andrea Arcangeli
2004-04-14 17:48       ` Hugh Dickins
2004-04-14 23:39         ` Andrea Arcangeli
2004-04-15 10:21           ` Hugh Dickins
2004-04-15 13:22             ` Andrea Arcangeli
2004-04-15 13:45               ` Hugh Dickins
2004-04-15 14:08                 ` Andrea Arcangeli [this message]
2004-04-15 16:23             ` Bill Davidsen
2004-04-15 16:48               ` Hugh Dickins
2004-04-22 19:54                 ` Bill Davidsen
2004-04-22 21:26                   ` Hugh Dickins
2004-04-14 18:11   ` Bill Davidsen

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=20040415140851.GF2150@dualathlon.random \
    --to=andrea@suse.de \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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