Thread (9 messages) 9 messages, 4 authors, 2008-12-23

Re: [rfc][patch] unlock_page speedup

From: Andrew Morton <akpm@linux-foundation.org>
Date: 2008-12-19 08:00:11
Also in: linux-fsdevel

On Fri, 19 Dec 2008 08:53:28 +0100 Nick Piggin [off-list ref] wrote:
On Thu, Dec 18, 2008 at 11:35:49PM -0800, Andrew Morton wrote:
quoted
On Fri, 19 Dec 2008 08:29:09 +0100 Nick Piggin [off-list ref] wrote:
quoted
Introduce a new page flag, PG_waiters
Leaving how many?
Don't know...
Need to know!  page.flags is prime real estate and we should decide
whether gaining 2% in a particular microbenchmark is our best use of it
I thought the page-flags.h obfuscation project was
supposed to make that clearer to work out. There are what, 21 flags
used now. If everything is coded properly, then the memory model
should automatically kick its metadata out of page flags if it gets
too big.
That would be nice :)
But most likely it will just blow up.
If we use them all _now_, as I proposed, we'll find out about that.
Probably we want
at least a few flags for memory model on 32-bit for smaller systems
(big NUMA 32-bit systems probably don't matter much anymore).

quoted
 fs-cache wants to take two more.
fs-cache is getting merged?
See thread titled "Pull request for FS-Cache, including NFS patches"
Wow, I've wanted to review that.
That would be good.


--
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>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help