From: Harshitha Ramamurthy <hramamurthy@google.com>
To: Mina Almasry <almasrymina@google.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, io-uring@vger.kernel.org,
virtualization@lists.linux.dev, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Donald Hunter" <donald.hunter@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"Jeroen de Borst" <jeroendb@google.com>,
"Kuniyuki Iwashima" <kuniyu@amazon.com>,
"Willem de Bruijn" <willemb@google.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Pavel Begunkov" <asml.silence@gmail.com>,
"David Ahern" <dsahern@kernel.org>,
"Neal Cardwell" <ncardwell@google.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Shuah Khan" <shuah@kernel.org>,
sdf@fomichev.me, dw@davidwei.uk,
"Jamal Hadi Salim" <jhs@mojatatu.com>,
"Victor Nogueira" <victor@mojatatu.com>,
"Pedro Tammela" <pctammela@mojatatu.com>,
"Samiullah Khawaja" <skhawaja@google.com>
Subject: Re: [PATCH net-next v9 7/9] gve: add netmem TX support to GVE DQO-RDA mode
Date: Tue, 22 Apr 2025 16:00:42 -0700 [thread overview]
Message-ID: <CAEAWyHf7Qzi8CDBeRMB5nMvvNawrFrUCh52k4JevbSHX1Y=zcw@mail.gmail.com> (raw)
In-Reply-To: <CAHS8izNZXmG0bi15DpmX2EcococF2swM83Urk19aQBvz=z3nUQ@mail.gmail.com>
On Tue, Apr 22, 2025 at 2:30 PM Mina Almasry <almasrymina@google.com> wrote:
>
> On Tue, Apr 22, 2025 at 10:43 AM Harshitha Ramamurthy
> <hramamurthy@google.com> wrote:
> >
> > On Thu, Apr 17, 2025 at 4:15 PM Mina Almasry <almasrymina@google.com> wrote:
> > >
> > > Use netmem_dma_*() helpers in gve_tx_dqo.c DQO-RDA paths to
> > > enable netmem TX support in that mode.
> > >
> > > Declare support for netmem TX in GVE DQO-RDA mode.
> > >
> > > Signed-off-by: Mina Almasry <almasrymina@google.com>
> > >
> > > ---
> > >
> > > v4:
> > > - New patch
> > > ---
> > > drivers/net/ethernet/google/gve/gve_main.c | 4 ++++
> > > drivers/net/ethernet/google/gve/gve_tx_dqo.c | 8 +++++---
> > > 2 files changed, 9 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/net/ethernet/google/gve/gve_main.c b/drivers/net/ethernet/google/gve/gve_main.c
> > > index 8aaac9101377..430314225d4d 100644
> > > --- a/drivers/net/ethernet/google/gve/gve_main.c
> > > +++ b/drivers/net/ethernet/google/gve/gve_main.c
> > > @@ -2665,6 +2665,10 @@ static int gve_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
> > >
> > > dev_info(&pdev->dev, "GVE version %s\n", gve_version_str);
> > > dev_info(&pdev->dev, "GVE queue format %d\n", (int)priv->queue_format);
> > > +
> > > + if (!gve_is_gqi(priv) && !gve_is_qpl(priv))
> > > + dev->netmem_tx = true;
> > > +
> >
> > a nit: but it would fit in better and be more uniform if this is set
> > earlier in the function where other features are set for the
> > net_device.
> >
>
> Thanks for taking a look. I actually thought about that while trying
> to implement this, but AFAIU (correct if wrong), gve_is_gqi and
> gve_is_qpl need priv to be initialized, so this feature set must be
> performed after gve_init_priv in this function. I suppose this feature
> checking maybe can be put before register_netdev. Do you prefer that?
Ah yes, you are right. Thanks for checking. That would be preferable.
Another option is to move it inside gve_init_priv() after the mode has
been set. Either is okay.
Thanks,
Harshitha
>
>
> --
> Thanks,
> Mina
next prev parent reply other threads:[~2025-04-22 23:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 23:15 [PATCH net-next v9 0/9] Device memory TCP TX Mina Almasry
2025-04-17 23:15 ` [PATCH net-next v9 1/9] netmem: add niov->type attribute to distinguish different net_iov types Mina Almasry
2025-04-22 8:17 ` Pavel Begunkov
2025-04-22 14:03 ` Mina Almasry
2025-04-22 19:53 ` Pavel Begunkov
2025-04-22 20:46 ` Mina Almasry
2025-04-17 23:15 ` [PATCH net-next v9 2/9] net: add get_netmem/put_netmem support Mina Almasry
2025-04-22 8:45 ` Pavel Begunkov
2025-04-22 13:56 ` Mina Almasry
2025-04-22 18:20 ` Pavel Begunkov
2025-04-22 18:30 ` Mina Almasry
2025-04-22 19:47 ` Pavel Begunkov
2025-04-22 20:04 ` Pavel Begunkov
2025-04-22 21:10 ` Mina Almasry
2025-04-23 10:49 ` Pavel Begunkov
2025-04-17 23:15 ` [PATCH net-next v9 3/9] net: devmem: TCP tx netlink api Mina Almasry
2025-04-17 23:15 ` [PATCH net-next v9 4/9] net: devmem: Implement TX path Mina Almasry
2025-04-17 23:15 ` [PATCH net-next v9 5/9] net: add devmem TCP TX documentation Mina Almasry
2025-04-17 23:15 ` [PATCH net-next v9 6/9] net: enable driver support for netmem TX Mina Almasry
2025-04-17 23:15 ` [PATCH net-next v9 7/9] gve: add netmem TX support to GVE DQO-RDA mode Mina Almasry
2025-04-22 17:43 ` Harshitha Ramamurthy
2025-04-22 21:30 ` Mina Almasry
2025-04-22 23:00 ` Harshitha Ramamurthy [this message]
2025-04-17 23:15 ` [PATCH net-next v9 8/9] net: check for driver support in netmem TX Mina Almasry
2025-04-17 23:15 ` [PATCH net-next v9 9/9] selftests: ncdevmem: Implement devmem TCP TX Mina Almasry
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='CAEAWyHf7Qzi8CDBeRMB5nMvvNawrFrUCh52k4JevbSHX1Y=zcw@mail.gmail.com' \
--to=hramamurthy@google.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=horms@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=jasowang@redhat.com \
--cc=jeroendb@google.com \
--cc=jhs@mojatatu.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mst@redhat.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=sdf@fomichev.me \
--cc=sgarzare@redhat.com \
--cc=shuah@kernel.org \
--cc=skhawaja@google.com \
--cc=stefanha@redhat.com \
--cc=victor@mojatatu.com \
--cc=virtualization@lists.linux.dev \
--cc=willemb@google.com \
--cc=xuanzhuo@linux.alibaba.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