Re: [PATCH] mm: implement swap prefetching

Paul Jackson
2006-02-08T04:46:55Z

Con, responding to Nick:
> > It introduces global cacheline bouncing in pagecache allocation and removal
> > and page reclaim paths, also low watermark failure is quite common in
> > normal operation, so that is another global cacheline write in page
> > allocation path.
>
> None of these issues is going to remotely the target audience. If the issue is
> how scalable such a change can be then I cannot advocate making the code
> smart and complex enough to be numa and cpuset aware.. but then that's never
> going to be the target audience. It affects a particular class of user which
> happens to be quite a large population not affected by complex memory
> hardware.

How about only moving memory back to the Memory Node (zone) that it
came from? And providing some call that Christoph Lameters migration
code can call, to disable or fix this up, so you don't end up bringing
back pages on their pre-migration nodes?

Just honoring the memory node placement should be sufficient. No need
to wrap your head around cpusets.

If you don't do that, then consider disabling this thing entirely
if CONFIG_NUMA is enabled. This swap prefetching sounds like it
could be a loose canon ball in a NUMA box.

As for non-NUMA boxes, like my humble desktop PC, I would -love-
to have Firefox come back up faster in the morning. I have a nightly
cron jobs push everything out to swap, and it is slow going getting it
back.

The day will come (it has already gotten there for some of my
colleagues who are using a small Altix system for their desktop
software) when we want this prefetching for NUMA boxes too.

--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401