From: Rushil Gupta <rushilg@google.com>
To: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
willemb@google.com, edumazet@google.com, pabeni@redhat.com
Cc: Rushil Gupta <rushilg@google.com>
Subject: [PATCH net-next 0/4] Add QPL mode for DQO descriptor format
Date: Wed, 2 Aug 2023 21:33:34 +0000 [thread overview]
Message-ID: <20230802213338.2391025-1-rushilg@google.com> (raw)
GVE supports QPL ("queue-page-list") mode where
all data is communicated through a set of pre-registered
pages. Adding this mode to DQO.
Rushil Gupta (4):
gve: Control path for DQO-QPL
gve: Tx path for DQO-QPL
gve: RX path for DQO-QPL
gve: update gve.rst
.../device_drivers/ethernet/google/gve.rst | 9 +
drivers/net/ethernet/google/gve/gve.h | 112 ++++-
drivers/net/ethernet/google/gve/gve_adminq.c | 93 +++-
drivers/net/ethernet/google/gve/gve_adminq.h | 10 +
drivers/net/ethernet/google/gve/gve_main.c | 20 +-
drivers/net/ethernet/google/gve/gve_rx_dqo.c | 126 +++++-
drivers/net/ethernet/google/gve/gve_tx_dqo.c | 404 ++++++++++++++----
7 files changed, 653 insertions(+), 121 deletions(-)
--
2.41.0.585.gd2178a4bd4-goog
next reply other threads:[~2023-08-02 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 21:33 Rushil Gupta [this message]
2023-08-02 21:33 ` [PATCH net-next 1/4] gve: Control path for DQO-QPL Rushil Gupta
2023-08-03 1:56 ` Jesse Brandeburg
2023-08-03 19:18 ` Rushil Gupta
2023-08-03 9:28 ` Simon Horman
2023-08-02 21:33 ` [PATCH net-next 2/4] gve: Tx " Rushil Gupta
2023-08-02 21:33 ` [PATCH net-next 3/4] gve: RX " Rushil Gupta
2023-08-02 21:33 ` [PATCH net-next 4/4] gve: update gve.rst Rushil Gupta
-- strict thread matches above, loose matches on Subject: below --
2023-08-01 21:54 [PATCH net-next 0/4] Add QPL mode for DQO descriptor format Rushil Gupta
2023-08-01 22:12 ` Jakub Kicinski
2023-08-01 23:12 ` Rushil Gupta
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=20230802213338.2391025-1-rushilg@google.com \
--to=rushilg@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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).