All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Stanislav Fomichev <stfomichev@gmail.com>
Cc: Stanislav Fomichev <sdf@fomichev.me>,
	netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, Saeed Mahameed <saeed@kernel.org>
Subject: Re: [PATCH net-next v4 10/12] net: dummy: add dummy shaper API
Date: Wed, 19 Feb 2025 09:36:26 -0800	[thread overview]
Message-ID: <20250219093626.08cbe243@kernel.org> (raw)
In-Reply-To: <Z7VkiOkRxL3vOL0G@mini-arch>

On Tue, 18 Feb 2025 20:56:40 -0800 Stanislav Fomichev wrote:
> On 02/18, Jakub Kicinski wrote:
> > On Mon, 17 Feb 2025 18:09:46 -0800 Stanislav Fomichev wrote:  
> > > A lot of selftests are using dummy module, convert it to netdev
> > > instance lock to expand the test coverage.  
> > 
> > I think the next version should be ready for merging.
> > What should we do with this patch?
> > Can we add a bool inside struct net_device to opt-in
> > for the ndo locking, without having to declare empty
> > ops? I think more drivers could benefit from it that way.  
> 
> Awesome, will drop this patch and add another one with a bool opt-in!
> 
> LMK if you prefer other name or a better comment:
> 
> @@ -2456,6 +2456,12 @@ struct net_device {
>          */
>         bool                    up;
> 
> +       /**
> +        * @request_ops_lock: request the core to run all @netdev_ops and
> +        * @ethtool_ops under the @lock.
> +        */
> +       bool                    request_ops_lock;
> +
>         /**
>          * @lock: netdev-scope lock, protects a small selection of fields.
>          * Should always be taken using netdev_lock() / netdev_unlock() helpers.
> 

Sure, SGTM

  reply	other threads:[~2025-02-19 17:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18  2:09 [PATCH net-next v4 00/12] net: Hold netdev instance lock during ndo operations Stanislav Fomichev
2025-02-18  2:09 ` [PATCH net-next v4 01/12] net: hold netdev instance lock during ndo_open/ndo_stop Stanislav Fomichev
2025-02-18  2:09 ` [PATCH net-next v4 02/12] net: hold netdev instance lock during ndo_setup_tc Stanislav Fomichev
2025-02-18  2:09 ` [PATCH net-next v4 03/12] net: hold netdev instance lock during queue operations Stanislav Fomichev
2025-02-18  2:09 ` [PATCH net-next v4 04/12] net: hold netdev instance lock during rtnetlink operations Stanislav Fomichev
2025-02-18  2:09 ` [PATCH net-next v4 05/12] net: hold netdev instance lock during ioctl operations Stanislav Fomichev
2025-02-18  2:09 ` [PATCH net-next v4 06/12] net: hold netdev instance lock during sysfs operations Stanislav Fomichev
2025-02-18  2:09 ` [PATCH net-next v4 07/12] net: hold netdev instance lock during ndo_bpf Stanislav Fomichev
2025-02-19  3:02   ` Jakub Kicinski
2025-02-19  4:54     ` Stanislav Fomichev
2025-02-18  2:09 ` [PATCH net-next v4 08/12] net: ethtool: try to protect all callback with netdev instance lock Stanislav Fomichev
2025-02-18  2:09 ` [PATCH net-next v4 09/12] net: replace dev_addr_sem " Stanislav Fomichev
2025-02-18  2:09 ` [PATCH net-next v4 10/12] net: dummy: add dummy shaper API Stanislav Fomichev
2025-02-19  3:09   ` Jakub Kicinski
2025-02-19  4:56     ` Stanislav Fomichev
2025-02-19 17:36       ` Jakub Kicinski [this message]
2025-02-18  2:09 ` [PATCH net-next v4 11/12] docs: net: document new locking reality Stanislav Fomichev
2025-02-19  2:53   ` Jakub Kicinski
2025-02-19  4:52     ` Stanislav Fomichev
2025-02-19  8:37   ` Paolo Abeni
2025-02-19 15:43     ` Stanislav Fomichev
2025-02-18  2:09 ` [PATCH net-next v4 12/12] eth: bnxt: remove most dependencies on RTNL Stanislav Fomichev

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=20250219093626.08cbe243@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeed@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=stfomichev@gmail.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.