From: Jakub Kicinski <kuba@kernel.org>
To: I Viswanath <viswanathiyyappan@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, sdf@fomichev.me, kuniyu@google.com,
ahmed.zaki@intel.com, aleksander.lobakin@intel.com,
jacob.e.keller@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linux.dev,
david.hunter.linux@gmail.com, khalid@kernel.org
Subject: Re: [RFC/RFT PATCH net-next v3 1/2] net: Add ndo_write_rx_config and helper structs and functions:
Date: Thu, 30 Oct 2025 19:20:18 -0700 [thread overview]
Message-ID: <20251030192018.28dcd830@kernel.org> (raw)
In-Reply-To: <20251028174222.1739954-2-viswanathiyyappan@gmail.com>
On Tue, 28 Oct 2025 23:12:21 +0530 I Viswanath wrote:
> @@ -1421,6 +1426,7 @@ struct net_device_ops {
> void (*ndo_change_rx_flags)(struct net_device *dev,
> int flags);
> void (*ndo_set_rx_mode)(struct net_device *dev);
> + void (*ndo_write_rx_config)(struct net_device *dev);
> int (*ndo_set_mac_address)(struct net_device *dev,
> void *addr);
> int (*ndo_validate_addr)(struct net_device *dev);
> @@ -1767,6 +1773,12 @@ enum netdev_reg_state {
> NETREG_DUMMY, /* dummy device for NAPI poll */
> };
>
> +struct rx_config_work {
pls make sure to prefix names of types and functions with netif,
netdev or net
> + struct work_struct config_write;
> + struct net_device *dev;
> + spinlock_t config_lock;
> +};
> +
> +#define update_snapshot(config_ptr, type) \
> + do { \
> + typeof((config_ptr)) rx_config = ((type *)(dev->priv))->rx_config; \
> + unsigned long flags; \
> + spin_lock_irqsave(&((dev)->rx_work->config_lock), flags); \
> + *rx_config = *(config_ptr); \
> + spin_unlock_irqrestore(&((dev)->rx_work->config_lock), flags); \
> + } while (0)
The driver you picked is relatively trivial, advanced drivers need
to sync longer lists of mcast / ucast addresses. Bulk of the complexity
is in keeping those lists. Simple
*rx_config = *(config_ptr);
assignment is not enough. The driver needs to know old and new entries
and send ADD/DEL commands to FW. Converting virtio_net would be better,
but it does one huge dump which is also not representative of most
advanced NICs.
> @@ -11961,9 +11989,17 @@ struct net_device *alloc_netdev_mqs(int sizeof_priv, const char *name,
> refcount_set(&dev->dev_refcnt, 1);
> #endif
>
> - if (dev_addr_init(dev))
> + dev->rx_work = kmalloc(sizeof(*dev->rx_work), GFP_KERNEL);
Let's only allocate any extra state if driver has the NDO
> + if (!dev->rx_work)
> goto free_pcpu;
>
> + dev->rx_work->dev = dev;
> + spin_lock_init(&dev->rx_work->config_lock);
> + INIT_WORK(&dev->rx_work->config_write, execute_write_rx_config);
> +
> + if (dev_addr_init(dev))
> + goto free_rx_work;
> +
> dev_mc_init(dev);
> dev_uc_init(dev);
>
> @@ -12045,6 +12081,10 @@ struct net_device *alloc_netdev_mqs(int sizeof_priv, const char *name,
> free_netdev(dev);
> return NULL;
>
> +free_rx_work:
> + cancel_work_sync(&dev->rx_work->config_write);
> + kfree(dev->rx_work);
> +
> free_pcpu:
> #ifdef CONFIG_PCPU_DEV_REFCNT
> free_percpu(dev->pcpu_refcnt);
> @@ -12130,6 +12170,9 @@ void free_netdev(struct net_device *dev)
> return;
> }
>
> + cancel_work_sync(&dev->rx_work->config_write);
> + kfree(dev->rx_work);
We need to shut down sooner, some time between ndo_stop and ndo_uninit
next prev parent reply other threads:[~2025-10-31 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 17:42 [RFC/RFT PATCH net-next v3 0/2] net: Split ndo_set_rx_mode into snapshot and deferred write I Viswanath
2025-10-28 17:42 ` [RFC/RFT PATCH net-next v3 1/2] net: Add ndo_write_rx_config and helper structs and functions: I Viswanath
2025-10-31 2:20 ` Jakub Kicinski [this message]
2025-10-28 17:42 ` [RFC/RFT PATCH net-next v3 2/2] net: ethernet: Implement ndo_write_rx_config callback for the 8139cp driver I Viswanath
2025-10-29 4:48 ` [RFC/RFT PATCH net-next v3 0/2] net: Split ndo_set_rx_mode into snapshot and deferred write I Viswanath
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=20251030192018.28dcd830@kernel.org \
--to=kuba@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=david.hunter.linux@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=khalid@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=skhan@linuxfoundation.org \
--cc=viswanathiyyappan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).