From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 373] i40e: TSO breaks for packets larger than 16k
Date: Mon, 02 Dec 2019 12:14:39 +0000 [thread overview]
Message-ID: <bug-373-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=373
Bug ID: 373
Summary: i40e: TSO breaks for packets larger than 16k
Product: DPDK
Version: 19.08
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: joerg.dpdk@thalheim.io
Target Milestone: ---
According to the linux kernel the maximum buffer size per descriptor is 16k
(https://github.com/torvalds/linux/blob/596cf45cbf6e4fa7bcb0df33e373a7d062b644b5/drivers/net/ethernet/intel/i40e/i40e_txrx.h#L226).
Buffers beyond that size are distributed over multiple descriptors:
https://github.com/torvalds/linux/blob/596cf45cbf6e4fa7bcb0df33e373a7d062b644b5/drivers/net/ethernet/intel/i40e/i40e_txrx.c#L3393
DPDK however does not perform this distribution:
https://github.com/DPDK/dpdk/blob/7001c8fdb27357c67147c0a13cb3826e48c0f2bf/drivers/net/i40e/i40e_rxtx.c#L1151
This results in DPDK stop processing packets once a buffer larger 16k is
en-queued.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-12-02 12:14 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-373-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).