[PATCH net-next 0/9] selective (per/namespace) flush of rt_cache
Eric W. Biederman
ebiederm at xmission.com
Mon Jul 7 03:29:23 PDT 2008
David Miller <davem at davemloft.net> writes:
> From: "Denis V. Lunev" <den at openvz.org>
> Date: Fri, 04 Jul 2008 17:16:00 +0400
>> This series of patches implements selective rt cache flushing to make
>> sure that in one namespace we'll not been able to affect the performance
>> of other from the user space.
> Applied and pushed out to net-next-2.6, thanks.
> Although I wish patch 9 didn't have to be so ugly. :-/ Also, is it
> really the right thing to do if another namespace's RT cache entries
> are in fact chewing up all the slots in a hash chain? I think
> the replacement garbage collection algorithm should be namespace
My VM experience agrees. The requested flushes from inside the namespace
and for namespace exit really should just flush the routes for that namespace.
However for general route caching and expiry I don't see the point of making
the code per namespace, and my gut feel is that is likely to reduce average
case performance at the cost of better isolation between namespaces.
Denis did I read the patches right and you are making all route cache flushes
per namespace? Including the periodic expiry?
More information about the Containers