Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758247Ab3CTQhJ (ORCPT ); Wed, 20 Mar 2013 12:37:09 -0400 Received: from mail-la0-f52.google.com ([209.85.215.52]:46620 "EHLO mail-la0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753605Ab3CTQhH (ORCPT ); Wed, 20 Mar 2013 12:37:07 -0400 MIME-Version: 1.0 In-Reply-To: <20130320.121704.1797978839297064162.davem@davemloft.net> References: <201303192143.r2JLhZIX020469@farm-0021.internal.tilera.com> <20130320.121704.1797978839297064162.davem@davemloft.net> Date: Wed, 20 Mar 2013 17:37:04 +0100 Message-ID: Subject: Re: [PATCH] dynticks: avoid flow_cache_flush() interrupting every core From: Frederic Weisbecker To: David Miller Cc: cmetcalf@tilera.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, gilad@benyossef.com, sasha.levin@oracle.com, akpm@linux-foundation.org, paulmck@linux.vnet.ibm.com, yoshfuji@linux-ipv6.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1367 Lines: 32 2013/3/20 David Miller : > From: Chris Metcalf > Date: Tue, 19 Mar 2013 17:35:58 -0400 > >> Previously, if you did an "ifconfig down" or similar on one core, and >> the kernel had CONFIG_XFRM enabled, every core would be interrupted to >> check its percpu flow list for items that could be garbage collected. >> >> With this change, we generate a mask of cores that actually have any >> percpu items, and only interrupt those cores. When we are trying to >> isolate a set of cpus from interrupts, this is important to do. >> >> Signed-off-by: Chris Metcalf >> --- >> This change stands alone so could be taken into the net tree if >> desired, but it is most useful in the context of Frederic Weisbecker's >> linux-dynticks work. So it could be taken up through either tree, >> but it certainly needs sign-off from someone familiar with net/core/flow.c. > > I'm find with this going into the dynticks changes: > > Acked-by: David S. Miller At it looks pretty self-contained, can that perhaps go through the networking tree? Thanks. -- 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/