From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next 0/9] selective (per/namespace) flush of rt_cache Date: Sat, 05 Jul 2008 20:55:48 -0700 (PDT) Message-ID: <20080705.205548.122498335.davem@davemloft.net> References: <1215177360.27873.50.camel@iris.sw.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1215177360.27873.50.camel-aPCOdVxUTlgvJsYlp49lxw@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: containers.vger.kernel.org From: "Denis V. Lunev" 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 agnostic.