From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@osdl.org>, hugh@veritas.com
Cc: linux-mm@kvack.org
Subject: Re: 2.6.6-rc3-mm1
Date: Wed, 5 May 2004 16:14:16 +0100 [thread overview]
Message-ID: <20040505161416.A4008@infradead.org> (raw)
In-Reply-To: <20040430014658.112a6181.akpm@osdl.org>; from akpm@osdl.org on Fri, Apr 30, 2004 at 01:46:58AM -0700
On Fri, Apr 30, 2004 at 01:46:58AM -0700, Andrew Morton wrote:
> +rmap-14-i_shared_lock-fixes.patch
> +rmap-15-vma_adjust.patch
> +rmap-16-pretend-prio_tree.patch
> +rmap-17-real-prio_tree.patch
> +rmap-18-i_mmap_nonlinear.patch
> +rmap-19-arch-prio_tree.patch
>
> More VM work from Hugh
That's about 600 lines of additional code. And that prio tree code is
used a lot, so even worse for that caches.
Do we have some benchmarks of real-life situation where the prio trees
show a big enough improvement or some 'exploits' where the linear list
walking leads to DoS situtations?
The bases objrmap/anonrmap changes keep the LOC pretty much the same as
the old pte-chain based code, but this is really a whole lot of code bloating
up the kernel and I'd prefer to see some numbers before it's going in..
--
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 parent reply other threads:[~2004-05-05 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040430014658.112a6181.akpm@osdl.org>
2004-05-05 15:14 ` Christoph Hellwig [this message]
2004-05-05 16:09 ` 2.6.6-rc3-mm1 Hugh Dickins
2004-05-05 16:50 2.6.6-rc3-mm1 Rajesh Venkatasubramanian
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=20040505161416.A4008@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=hugh@veritas.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