From: "Arinzon, David" <darinzon@amazon.com>
To: Joe Damato <jdamato@fastly.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Agroskin, Shay" <shayagr@amazon.com>,
"Kiyanovski, Arthur" <akiyano@amazon.com>,
"Dagan, Noam" <ndagan@amazon.com>,
"Bshara, Saeed" <saeedb@amazon.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Kamal Heib <kheib@redhat.com>,
open list <linux-kernel@vger.kernel.org>,
"Bernstein, Amit" <amitbern@amazon.com>
Subject: RE: [net-next 2/2] ena: Link queues to NAPIs
Date: Tue, 1 Oct 2024 16:40:32 +0000 [thread overview]
Message-ID: <d631f97559534c058fbd5c95afcb807a@amazon.com> (raw)
> > > >
> > > > Thank you for uploading this patch.
> > >
> > > Can you please let me know (explicitly) if you want me to send a
> > > second revision (when net-next allows for it) to remove the 'struct
> > > napi_struct' and add a comment as described above?
> >
> > Yes, I would appreciate that.
> > I guess the `struct napi_struct` is OK, this way both functions will look the
> same.
> > Regarding the comment, yes please, something like /* This API is
> supported for non-XDP queues only */ in both places.
> > I also added a small request to preserve reverse christmas tree order on
> patch 1/2 in the series.
>
> Thanks for mentioning the nit about reverse christmas tree order; I missed
> that.
>
> I will:
> - Fix the ordering of the variables in 1/2
> - Add 2 comments in 2/2
>
> I'll have to wait the ~48hr timeout before I can post the v2, but I'll be sure to
> CC you on the next revision.
It's not at least a 24hr timeout?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/maintainer-netdev.rst#n394
>
> > Thank you again for the patches in the driver.
>
> No worries, thanks for the review.
>
> BTW: Since neither of the changes you've asked me to make are functional
> changes, would you mind testing the driver changes on your side just to
> make sure? I tested them myself on an ec2 instance with an ENA driver, but I
> am not an expert on ENA :)
>
> - Joe
I picked up the patch and got to the same results that you did when running on an EC2 instance.
Thank you for sharing the commands in the commit messages, it was really helpful.
Correct me if I'm wrong, but there's no functional impact to these changes except the ability to
view the mappings through netlink.
next reply other threads:[~2024-10-01 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 16:40 Arinzon, David [this message]
2024-10-01 18:07 ` [net-next 2/2] ena: Link queues to NAPIs Joe Damato
-- strict thread matches above, loose matches on Subject: below --
2024-09-30 19:56 [net-next 0/2] ena: Link IRQs, queues, and NAPI instances Joe Damato
2024-09-30 19:56 ` [net-next 2/2] ena: Link queues to NAPIs Joe Damato
2024-10-01 9:06 ` Arinzon, David
2024-10-01 14:28 ` Joe Damato
2024-10-01 15:50 ` Arinzon, David
2024-10-01 16:21 ` Joe Damato
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=d631f97559534c058fbd5c95afcb807a@amazon.com \
--to=darinzon@amazon.com \
--cc=akiyano@amazon.com \
--cc=amitbern@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdamato@fastly.com \
--cc=kheib@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndagan@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedb@amazon.com \
--cc=shayagr@amazon.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).