[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241130124501.38b98030@kernel.org>
Date: Sat, 30 Nov 2024 12:45:01 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Joe Damato <jdamato@...tly.com>
Cc: Guenter Roeck <linux@...ck-us.net>, netdev@...r.kernel.org,
mkarsten@...terloo.ca, skhawaja@...gle.com, sdf@...ichev.me,
bjorn@...osinc.com, amritha.nambiar@...el.com, sridhar.samudrala@...el.com,
willemdebruijn.kernel@...il.com, edumazet@...gle.com, "David S. Miller"
<davem@...emloft.net>, Paolo Abeni <pabeni@...hat.com>, Jonathan Corbet
<corbet@....net>, Jiri Pirko <jiri@...nulli.us>, Sebastian Andrzej Siewior
<bigeasy@...utronix.de>, Lorenzo Bianconi <lorenzo@...nel.org>, Johannes
Berg <johannes.berg@...el.com>, "open list:DOCUMENTATION"
<linux-doc@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>,
pcnet32@...ntier.com
Subject: Re: [net-next v6 5/9] net: napi: Add napi_config
On Wed, 27 Nov 2024 12:00:02 -0800 Joe Damato wrote:
> CPU 0:
> pcnet32_open
> lock(lp->lock)
> napi_enable
> napi_hash_add <- before this executes, CPU 1 proceeds
> lock(napi_hash_lock)
> CPU 1:
> pcnet32_close
> napi_disable
> napi_hash_del
> lock(napi_hash_lock)
> < INTERRUPT >
How about making napi_hash_lock irq-safe ?
It's a control path lock, it should be fine to disable irqs.
> pcnet32_interrupt
> lock(lp->lock)
Powered by blists - more mailing lists