From: Leon Romanovsky <leon@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
kuba@kernel.org, keescook@chromium.org,
"open list:HFI1 DRIVER" <linux-rdma@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] IB/hfi1: allocate dummy net_device dynamically
Date: Sun, 17 Mar 2024 10:41:44 +0200 [thread overview]
Message-ID: <20240317084144.GF12921@unreal> (raw)
In-Reply-To: <ZfSKskdFpbGVgnk4@gmail.com>
On Fri, Mar 15, 2024 at 10:51:46AM -0700, Breno Leitao wrote:
> On Fri, Mar 15, 2024 at 12:12:15PM -0400, Dennis Dalessandro wrote:
> > On 3/13/24 6:33 AM, Breno Leitao wrote:
> > > struct net_device shouldn't be embedded into any structure, instead,
> > > the owner should use the priv space to embed their state into net_device.
> > >
> > > Embedding net_device into structures prohibits the usage of flexible
> > > arrays in the net_device structure. For more details, see the discussion
> > > at [1].
> > >
> > > Un-embed the net_device from struct hfi1_netdev_rx by converting it
> > > into a pointer. Then use the leverage alloc_netdev() to allocate the
> > > net_device object at hfi1_alloc_rx().
> > >
> > > [1] https://lore.kernel.org/all/20240229225910.79e224cf@kernel.org/
> > >
> > > Signed-off-by: Breno Leitao <leitao@debian.org>
> > >
> > > ----
> > > PS: this diff needs d160c66cda0ac8614 ("net: Do not return value from
> > > init_dummy_netdev()") in order to apply and build cleanly.
> > > ---
> > > Changelog:
> > >
> > > v2:
> > > * Free struct hfi1_netdev_rx allocation if alloc_netdev() fails
> > > * Pass zero as the private size for alloc_netdev().
> > > * Remove wrong reference for iwl in the comments
> > > ---
> >
> > Very lightly tested, but interface came up and I could send traffic. Code seems
> > OK too.
> >
> > I'd prefer to at least remove the first sentence of the commit message.
>
> That is OK for me. Would you like to remove it when merging it, or,
> would you prefer me to resend it?
Please resend together with Dennis's Acked-by.
Thanks
>
> Thanks
prev parent reply other threads:[~2024-03-17 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 10:33 [PATCH v2] IB/hfi1: allocate dummy net_device dynamically Breno Leitao
2024-03-13 10:42 ` Leon Romanovsky
2024-03-13 13:55 ` Jakub Kicinski
2024-03-13 17:16 ` Leon Romanovsky
2024-03-15 16:12 ` Dennis Dalessandro
2024-03-15 17:51 ` Breno Leitao
2024-03-17 8:41 ` Leon Romanovsky [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=20240317084144.GF12921@unreal \
--to=leon@kernel.org \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=jgg@ziepe.ca \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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