On Tue, 2006-09-12 at 21:29 -0400, Rik van Riel wrote:
> Note that the transition _to_ volatile can also be batched
> and done somewhat lazily. For frequently mmaped pages that
> could end up saving us the transition the other way, too...
That would be helpful, only how to do it? We need some sort of list or
array where to store the pages that should be made volatile. The main
problem that I see is that you have to remove a page that is freed from
the list/array again, otherwise you would end up with a non page-cache
page being made volatile. That makes using per-cpu arrays hard since a
page can be freed on another cpu.
--
blue skies,
Martin.
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
"Reality continues to ruin my life." - Calvin.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
