From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Breno Leitao <leitao@debian.org>
Cc: <kuba@kernel.org>, <davem@davemloft.net>, <pabeni@redhat.com>,
<edumazet@google.com>, <elder@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <nbd@nbd.name>,
<sean.wang@mediatek.com>, <Mark-MC.Lee@mediatek.com>,
<lorenzo@kernel.org>, <taras.chornyi@plvision.eu>,
<quic_jjohnson@quicinc.com>, <kvalo@kernel.org>,
<leon@kernel.org>, <dennis.dalessandro@cornelisnetworks.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>, Jiri Pirko <jiri@resnulli.us>,
Simon Horman <horms@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH net-next v3 1/5] net: create a dummy net_device allocator
Date: Thu, 4 Apr 2024 18:40:33 +0200 [thread overview]
Message-ID: <1b1dfe1f-57ed-416d-a9c0-408aafa69583@intel.com> (raw)
In-Reply-To: <20240404114854.2498663-2-leitao@debian.org>
From: Breno Leitao <leitao@debian.org>
Date: Thu, 4 Apr 2024 04:48:41 -0700
> It is impossible to use init_dummy_netdev together with alloc_netdev()
> as the 'setup' argument.
>
> This is because alloc_netdev() initializes some fields in the net_device
> structure, and later init_dummy_netdev() memzero them all. This causes
> some problems as reported here:
>
> https://lore.kernel.org/all/20240322082336.49f110cc@kernel.org/
>
> Split the init_dummy_netdev() function in two. Create a new function called
> init_dummy_netdev_core() that does not memzero the net_device structure.
> Then have init_dummy_netdev() memzero-ing and calling
> init_dummy_netdev_core(), keeping the old behaviour.
>
> init_dummy_netdev_core() is the new function that could be called as an
> argument for alloc_netdev().
>
> Also, create a helper to allocate and initialize dummy net devices,
> leveraging init_dummy_netdev_core() as the setup argument. This function
> basically simplify the allocation of dummy devices, by allocating and
> initializing it. Freeing the device continue to be done through
> free_netdev()
[...]
> @@ -11063,6 +11070,17 @@ void free_netdev(struct net_device *dev)
> }
> EXPORT_SYMBOL(free_netdev);
>
> +/**
> + * alloc_netdev_dummy - Allocate and initialize a dummy net device.
> + * @sizeof_priv: size of private data to allocate space for
> + */
> +struct net_device *alloc_netdev_dummy(int sizeof_priv)
Repeating my question from the previous thread: I see that in your
series you always pass 0 as @sizeof_priv, does it make sense to have
this argument or we can just pass 0 here to alloc_netdev() unconditionally?
Drivers that have &net_device embedded can't have any private data there
anyway.
> +{
> + return alloc_netdev(sizeof_priv, "dummy#", NET_NAME_UNKNOWN,
> + init_dummy_netdev_core);
> +}
> +EXPORT_SYMBOL_GPL(alloc_netdev_dummy);
> +
> /**
> * synchronize_net - Synchronize with packet receive processing
> *
Thanks,
Olek
next prev parent reply other threads:[~2024-04-04 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 11:48 [PATCH net-next v3 0/5] allocate dummy device dynamically Breno Leitao
2024-04-04 11:48 ` [PATCH net-next v3 1/5] net: create a dummy net_device allocator Breno Leitao
2024-04-04 16:40 ` Alexander Lobakin [this message]
2024-04-04 19:03 ` Breno Leitao
2024-04-04 11:48 ` [PATCH net-next v3 2/5] net: marvell: prestera: allocate dummy net_device dynamically Breno Leitao
2024-04-04 11:59 ` [EXTERNAL] " Elad Nachman
2024-04-04 11:48 ` [PATCH net-next v3 3/5] net: mediatek: mtk_eth_sock: " Breno Leitao
2024-04-04 11:48 ` [PATCH net-next v3 4/5] net: ipa: " Breno Leitao
2024-04-04 11:48 ` [PATCH net-next v3 5/5] net: ibm/emac: " Breno Leitao
2024-04-04 11:59 ` [PATCH net-next v3 0/5] allocate dummy device dynamically Kalle Valo
2024-04-04 14:22 ` Breno Leitao
2024-04-04 15:01 ` Kalle Valo
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=1b1dfe1f-57ed-416d-a9c0-408aafa69583@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=Mark-MC.Lee@mediatek.com \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=leitao@debian.org \
--cc=leon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_jjohnson@quicinc.com \
--cc=sean.wang@mediatek.com \
--cc=taras.chornyi@plvision.eu \
/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
all inboxes | Powered by JetHome®