[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20160401.151820.127036849232206611.davem@davemloft.net>
Date: Fri, 01 Apr 2016 15:18:20 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: mw@...ihalf.com
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
netdev@...r.kernel.org, linux@....linux.org.uk,
sebastian.hesselbarth@...il.com, andrew@...n.ch,
jason@...edaemon.net, thomas.petazzoni@...e-electrons.com,
gregory.clement@...e-electrons.com, nadavh@...vell.com,
alior@...vell.com, nitroshift@...oo.com, jaz@...ihalf.com
Subject: Re: [PATCH] net: mvneta: fix changing MTU when using per-cpu
processing
From: Marcin Wojtas <mw@...ihalf.com>
Date: Fri, 1 Apr 2016 15:21:18 +0200
> After enabling per-cpu processing it appeared that under heavy load
> changing MTU can result in blocking all port's interrupts and transmitting
> data is not possible after the change.
>
> This commit fixes above issue by disabling percpu interrupts for the
> time, when TXQs and RXQs are reconfigured.
>
> Signed-off-by: Marcin Wojtas <mw@...ihalf.com>
Applied, thanks.
When I reviewed this I was worried that this was yet another case where
the ndo op could be invoked in a potentially atomic or similar context,
whereby on_each_cpu() would be illegal to use.
But that appears to not be the case, and thus this change is just fine.
Thanks.
Powered by blists - more mailing lists