From: Kommula Shiva Shankar <kshankar@marvell.com>
To: <dev@dpdk.org>, <maxime.coquelin@redhat.com>, <chenbox@nvidia.com>
Cc: <david.marchand@redhat.com>, <jerinj@marvell.com>,
<ndabilpuram@marvell.com>, <schalla@marvell.com>
Subject: [PATCH] doc: update virtio prog guide with new feature list
Date: Tue, 4 Mar 2025 23:12:36 +0530 [thread overview]
Message-ID: <20250304174236.280764-1-kshankar@marvell.com> (raw)
This patch adds newly added virtio hash report feature
to prog guide.
Signed-off-by: Kommula Shiva Shankar <kshankar@marvell.com>
---
doc/guides/nics/virtio.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/guides/nics/virtio.rst b/doc/guides/nics/virtio.rst
index c22ce56a02..0615abfaaf 100644
--- a/doc/guides/nics/virtio.rst
+++ b/doc/guides/nics/virtio.rst
@@ -56,6 +56,7 @@ In this release, the virtio PMD provides the basic functionality of packet recep
command line. Note that, mac/vlan filter is best effort: unwanted packets could still arrive.
* "RTE_PKTMBUF_HEADROOM" should be defined
+ no less than "sizeof(struct virtio_net_hdr_hash_report)", which is 20 bytes when using hash report or
no less than "sizeof(struct virtio_net_hdr_mrg_rxbuf)", which is 12 bytes when mergeable or
"VIRTIO_F_VERSION_1" is set.
no less than "sizeof(struct virtio_net_hdr)", which is 10 bytes, when using non-mergeable.
@@ -68,6 +69,8 @@ In this release, the virtio PMD provides the basic functionality of packet recep
* Virtio supports software vlan stripping and inserting.
+* Virtio supports hash report feature in packed queue mode.
+
* Virtio supports using port IO to get PCI resource when UIO module is not available.
* Virtio supports RSS Rx mode with 40B configurable hash key length, 128
--
2.43.0
reply other threads:[~2025-03-04 17:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250304174236.280764-1-kshankar@marvell.com \
--to=kshankar@marvell.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=ndabilpuram@marvell.com \
--cc=schalla@marvell.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).