Re: [PATCH] dynticks: avoid flow_cache_flush() interrupting everycore
From: David Miller
Date: Wed Mar 20 2013 - 13:29:11 EST
From: Frederic Weisbecker <fweisbec@xxxxxxxxx>
Date: Wed, 20 Mar 2013 17:37:04 +0100
> 2013/3/20 David Miller <davem@xxxxxxxxxxxxx>:
>> From: Chris Metcalf <cmetcalf@xxxxxxxxxx>
>> 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 <cmetcalf@xxxxxxxxxx>
>>> 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 <davem@xxxxxxxxxxxxx>
> At it looks pretty self-contained, can that perhaps go through the
> networking tree?
Fair enough, applied to net-next, thanks.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/