Hi!

quoted text
> > > or
> > > 
> > >   - have a global reserve and selectively serves sockets
> > >     (what I've been doing)
> > 
> > That is a scalability problem on large systems! Global means global 
> > serialization, cacheline bouncing and possibly livelocks. If we get into 
> > this global shortage then all cpus may end up taking the same locks 
> > cycling thought the same allocation paths.
> 
> Dude, breathe, these boxens of yours will never swap over network simply
> because you never configure swap. 
> 
> And, _no_, it does not necessarily mean global serialisation. By simply
> saying there must be N pages available I say nothing about on which node
> they should be available, and the way the watermarks work they will be
> evenly distributed over the appropriate zones.

Agreed. Scalability of emergency swapping reserved is simply
unimportant. Please, lets get swapping to _work_ first, then we can
make it faster.

No, I do not think we'll ever see a livelock on this.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/