From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
jk@ozlabs.org, jes@trained-monkey.org, cpw@sgi.com
Subject: [patch 0/4] remove nopfn
Date: Fri, 2 May 2008 05:19:03 +0200 [thread overview]
Message-ID: <20080502031903.GD11844@wotan.suse.de> (raw)
Hi,
Can we pretty please get this into the current merge window? All it takes
is a quick review and test ;) I think mspec was already tested, but it
wouldn't hurt to verify again...
It shaves about .5K off mm/memory.o so it is pretty significant.
Mispredicted branches are also actually a significant cost in the fault
path which I'm trying to reduce (merging fault with page_mkwrite should
help with this further).
--
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 reply other threads:[~2008-05-02 3:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 3:19 Nick Piggin [this message]
2008-05-02 3:20 ` [patch 1/4] mm: allow pfnmap ->fault()s Nick Piggin
2008-05-02 3:21 ` [patch 2/4] mspec: convert nopfn to fault Nick Piggin
2008-05-06 12:27 ` Robin Holt
2008-05-02 3:22 ` [patch 3/4] spufs: " Nick Piggin
2008-05-02 4:06 ` Jeremy Kerr
2008-05-02 4:47 ` Nick Piggin
2008-05-02 9:43 ` Jeremy Kerr
2008-05-03 5:41 ` Nick Piggin
2008-05-06 3:01 ` Jeremy Kerr
2008-05-06 8:38 ` Nick Piggin
2008-05-02 5:06 ` Nick Piggin
2008-05-02 6:45 ` Jeremy Kerr
2008-05-02 3:23 ` [patch 4/4] mm: remove nopfn Nick Piggin
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=20080502031903.GD11844@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=cpw@sgi.com \
--cc=jes@trained-monkey.org \
--cc=jk@ozlabs.org \
--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