From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Junfeng Guo <junfeng.guo@intel.com>,
qi.z.zhang@intel.com, rushilg@google.com
Cc: dev@dpdk.org, joshwash@google.com, jeroendb@google.com
Subject: Re: [PATCH] net/gve: support queue start and stop operations
Date: Wed, 17 May 2023 23:30:48 +0100 [thread overview]
Message-ID: <1d4e08d4-c59a-b2a2-2903-50c4d942e847@amd.com> (raw)
In-Reply-To: <20230509030729.2680451-1-junfeng.guo@intel.com>
On 5/9/2023 4:07 AM, Junfeng Guo wrote:
> Add support for queue operations for GQI:
> - gve_rx_queue_start
> - gve_tx_queue_start
> - gve_rx_queue_stop
> - gve_tx_queue_stop
>
> Add support for queue operations for DQO:
> - gve_rx_queue_start_dqo
> - gve_tx_queue_start_dqo
> - gve_rx_queue_stop_dqo
> - gve_tx_queue_stop_dqo
>
> Also move the funcs of rxq_mbufs_alloc into the corresponding files.
>
> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
>
> Tested-by: Rushil Gupta <rushilg@google.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-05-17 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 3:07 Junfeng Guo
2023-05-15 20:28 ` Rushil Gupta
2023-05-17 22:30 ` Ferruh Yigit [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=1d4e08d4-c59a-b2a2-2903-50c4d942e847@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=jeroendb@google.com \
--cc=joshwash@google.com \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=rushilg@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).