From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/doc Bug 1485] Checksum function should require the whole packet to be on one segment
Date: Wed, 10 Jul 2024 01:52:34 +0000 [thread overview]
Message-ID: <bug-1485-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1485
Bug ID: 1485
Summary: Checksum function should require the whole packet to
be on one segment
Product: DPDK
Version: 24.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: doc
Assignee: dev@dpdk.org
Reporter: user202729@protonmail.com
Target Milestone: ---
The function rte_ipv4_udptcp_cksum (and probably also
rte_ipv4_udptcp_cksum_verify ) does not work properly when the header is taken
from a mbuf that consist of multiple segments.
I suggest editing the documentation to say e.g. "if the header is taken from a
mbuf with e.g. rte_pktmbuf_mtod which potentially consist of multiple segments,
use rte_ipv4_udptcp_cksum_mbuf instead."
Related:
https://inbox.dpdk.org/dev/20211015051306.320328-1-xiaoyun.li@intel.com/T/
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3048 bytes --]
reply other threads:[~2024-07-10 1:52 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-1485-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).