From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/doc Bug 1488] Suggestion: add documentation to fill in total_length etc. to UDP checksum offloading?
Date: Mon, 15 Jul 2024 04:22:13 +0000 [thread overview]
Message-ID: <bug-1488-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1488
Bug ID: 1488
Summary: Suggestion: add documentation to fill in total_length
etc. to UDP checksum offloading?
Product: DPDK
Version: 24.07
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: doc
Assignee: dev@dpdk.org
Reporter: user202729@protonmail.com
Target Milestone: ---
Currently, the documentation of RTE_MBUF_F_TX_UDP_CKSUM in
https://doc.dpdk.org/api/rte__mbuf__core_8h.html#ada511d6f30184b374ba2248c26af8ede
is very sparse:
> UDP cksum of TX pkt. computed by NIC.
I think it should mention which fields should be set.
Some bug reports e.g. https://github.com/amzn/amzn-drivers/issues/176
https://github.com/amzn/amzn-drivers/issues/79 states that you need to set
m3_len, total_length, dgram_cksum to the pseudo-header checksum etc. (not sure
about this).
What is the actual requirement of that flag, and how should the documentation
be edited?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3346 bytes --]
reply other threads:[~2024-07-15 4:22 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=bug-1488-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).