From: Jakub Kicinski <kuba@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: Jiri Pirko <jiri@resnulli.us>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Hillf Danton <hdanton@sina.com>,
Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH (EXPERIMENTAL)] team: replace term lock with rtnl lock
Date: Sat, 17 May 2025 08:09:48 -0700 [thread overview]
Message-ID: <20250517080948.3c20db08@kernel.org> (raw)
In-Reply-To: <ff1d684a-22ec-4ea2-a6ee-fe9704a6f284@I-love.SAKURA.ne.jp>
On Sat, 17 May 2025 16:32:20 +0900 Tetsuo Handa wrote:
> - if (!mutex_trylock(&team->lock)) {
> + /* Since this function is called from WQ context, RTNL can't be held by the caller. */
> + if (!rtnl_trylock()) {
> + /*
> + * Since RTNL is shared by many callers, and rtnl_unlock() is a slower operation
> + * than plain mutex_unlock(), rtnl_trylock() will be more easier to compate than
> + * mutex_trylock(). Therefore, we might want to delay a bit before retrying.
> + */
I think this was a trylock because there are places we try to cancel
this work while already holding the lock.
FWIW I'm not opposed to the patch. Could you wait a week and repost,
tho? We have a fix queued up in another tree - 6b1d3c5f675cc7
if we apply your patch to net-next there will be a build failure
on merge. Not a showstopper but we'll merge the trees on Thu so it
can be easily avoided if we wait until then.
next prev parent reply other threads:[~2025-05-17 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 7:32 [PATCH (EXPERIMENTAL)] team: replace term lock with rtnl lock Tetsuo Handa
2025-05-17 15:09 ` Jakub Kicinski [this message]
2025-05-21 13:54 ` Tetsuo Handa
2025-05-21 17:59 ` Jakub Kicinski
2025-05-20 9:23 ` Jiri Pirko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250517080948.3c20db08@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.