DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rajesh Kumar <rajesh3.kumar@intel.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, aman.deep.singh@intel.com
Subject: [PATCH v1 0/1] net/e1000: limit 2.5G inter-packet gap workaround to I225
Date: Fri, 13 Nov 2026 14:17:25 +0530	[thread overview]
Message-ID: <20261113084726.4059806-1-rajesh3.kumar@intel.com> (raw)

The igc link update path unconditionally widens the transmit
inter-packet gap (TIPG.IPGT 0x08 -> 0x0b, 12 -> 15 byte times)
whenever the link comes up at 2.5 Gb/s.

This is a workaround for an erratum in early I225 steppings, where
a back-to-back I225 receiver can drop packets arriving with an IPG
below 8 bytes. Applying it to every 2.5G-capable device costs about
0.2% of small-frame transmit rate on I226 and fixed I225 steppings,
which do not need it.

This patch gates the workaround on I225 device IDs with revision_id
below E1000_REVISION_2, and restores the default gap at other speeds
so a renegotiated link does not keep the widened value.

The igc driver has since been merged into net/e1000; this series is
based on that layout and uses the shared e1000 base definitions.

Rajesh Kumar (1):
  net/e1000: limit 2.5G inter-packet gap workaround to I225

 drivers/net/intel/e1000/igc_ethdev.c | 39 +++++++++++++++++++++++++---
 1 file changed, 36 insertions(+), 3 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-11-13  8:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13  8:47 Rajesh Kumar [this message]
2026-11-13  8:47 ` [PATCH v1 1/1] net/e1000: limit 2.5G inter-packet gap workaround to I225 Rajesh Kumar

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=20261113084726.4059806-1-rajesh3.kumar@intel.com \
    --to=rajesh3.kumar@intel.com \
    --cc=aman.deep.singh@intel.com \
    --cc=bruce.richardson@intel.com \
    --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