[lkml]   [2007]   [Apr]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/2] Optimize compound_head() by avoiding a shared page flag
On Sat, 7 Apr 2007, Andrew Morton wrote:

> Which is all a ton of fun, but this subversion of the architecture's
> freedom to use volatile, memory barriers etc is a worry. We do the same in
> page_alloc.c, of course...

I just tried the approach that we discussed earlier and it was not
nice either. Lets just use a page flag please. This check will be in
several hot code paths. And it may become more important because the file
system folks want to support buffers > page size. Then we may want more
transparent support for huge pages... For all of this page->private gets
in the way.

And I think we curently have 5 or so page flags available?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-04-08 02:25    [W:0.073 / U:0.364 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site