From: Bruce Richardson <bruce.richardson@intel.com>
To: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [PATCH v2] net/idpf: fix Tx of large mbuf segments
Date: Wed, 1 Jul 2026 10:47:57 +0100 [thread overview]
Message-ID: <akTiTRtGm_a954tE@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <838a36a9-654f-4b32-b3d4-3457dd024b58@intel.com>
On Wed, Jul 01, 2026 at 09:44:52AM +0100, Medvedkin, Vladimir wrote:
>
> On 7/1/2026 9:23 AM, Bruce Richardson wrote:
> > When TSO is enabled, and we get a packet to transmit where an individual
> > mbuf segment is longer than 16k, we need to split that segment across
> > multiple Tx descriptors. This support is present in the single-queue
> > mode of idpf - since it shares common code with the other Intel drivers
> > - but was missing from the splitq path.
> >
> > This patch adds the proper data path handling. Previous work ensured
> > that the descriptor count calculation took over-sized segments into
> > account but the actual descriptor writing part was overlooked.
> >
> > Fixes: 770f4dfe0f79 ("net/idpf: support basic Tx data path")
> > Fixes: 2904020f8313 ("net/intel: add common function to calculate needed descs")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Acked-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> > ---
> > V2: change check for number of free descriptor slots to use the correct
> > count, rather than just the number of mbuf segments passed
> > ---
> > drivers/net/intel/idpf/idpf_common_rxtx.c | 43 ++++++++++++++++++-----
> > 1 file changed, 35 insertions(+), 8 deletions(-)
> >
Patch applied to dpdk-next-net-intel.
/Bruce
prev parent reply other threads:[~2026-07-01 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 15:00 [PATCH] net/idpf: handle Tx of mbuf segments larger than 16k Bruce Richardson
2026-03-04 9:53 ` Bruce Richardson
2026-03-06 13:45 ` Burakov, Anatoly
2026-03-06 14:03 ` Burakov, Anatoly
2026-03-06 14:16 ` Burakov, Anatoly
2026-06-26 13:43 ` [PATCH] net/idpf: fix Tx of large mbuf segments Bruce Richardson
2026-06-30 17:35 ` Medvedkin, Vladimir
2026-07-01 8:23 ` [PATCH v2] " Bruce Richardson
2026-07-01 8:44 ` Medvedkin, Vladimir
2026-07-01 9:47 ` Bruce Richardson [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=akTiTRtGm_a954tE@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=vladimir.medvedkin@intel.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