From: Jakub Kicinski <kuba@kernel.org>
To: Qingfang Deng <dqfext@gmail.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-ppp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH net-next] ppp: enable TX scatter-gather
Date: Wed, 17 Sep 2025 14:14:34 -0700 [thread overview]
Message-ID: <20250917141434.596f6b8b@kernel.org> (raw)
In-Reply-To: <CALW65jZaDtchy1FFttNH9jMo--YSoZMsb8=HE72i=ZdnNP-akw@mail.gmail.com>
On Wed, 17 Sep 2025 19:00:16 +0800 Qingfang Deng wrote:
> On Tue, Sep 16, 2025 at 10:57 PM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > On Tue, 16 Sep 2025 10:57:49 +0800 Qingfang Deng wrote:
> > > Can I modify dev->features directly under the spin lock (without
> > > .ndo_fix_features) ?
> >
> > Hm, I'm not aware of a reason not to. You definitely need to hold
> > rtnl_lock, and call netdev_update_features() after.
>
> Will the modification race against __netdev_update_features(), where
> dev->features is assigned a new value?
Shouldn't race if we're holding rtnl_lock when we make the modification
and until we call netdev_update_features()? I'm just spitballing tho,
haven't studied the code.
prev parent reply other threads:[~2025-09-17 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 9:59 [PATCH net-next] ppp: enable TX scatter-gather Qingfang Deng
2025-09-16 1:10 ` Jakub Kicinski
2025-09-16 2:57 ` Qingfang Deng
2025-09-16 14:57 ` Jakub Kicinski
2025-09-17 11:00 ` Qingfang Deng
2025-09-17 21:14 ` Jakub Kicinski [this message]
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=20250917141434.596f6b8b@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.