News for hackers. Stuff that matters.
Re:What's wrong with 1975 programming by jacquesm on Wednesday July 28, 2010 @05:53PM (#1555800)
The whole point of this article - and it is a very good point - is that keeping your cache in user-space is not the right way to approach the problem. And you can get multiple hits anyway if you make sure that data that will expire together will end up in the same page.

Your other description does not match the use case of a production web server running varnish instances as the front-end.

Re:What's wrong with 1975 programming by haberman on Wednesday July 28, 2010 @06:07PM (#1555837)
The whole point of my comment is that PHK's analysis leaves out many downsides of leaving it all to the kernel.

His main argument against doing it is user-space is that you will "fight with the kernel's elaborate memory management." But if you just turn off swap completely and read files with read/write instead of mmap(), there is no fight. Everything happens in user-space.

Leaving it all to the kernel has many disadvantages as I spent many paragraphs explaining.

Re:What's wrong with 1975 programming by jacquesm on Wednesday July 28, 2010 @06:11PM (#1555846)
I missed the 'if you just turn off swap completely' bit in the paragraphs above.

Edit: even on re-reading it all I can't find it.