All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1638] Differences in how different Intel NICs handle maximum packet length for jumbo frame
Date: Mon, 03 Feb 2025 03:05:55 +0000	[thread overview]
Message-ID: <bug-1638-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1638

            Bug ID: 1638
           Summary: Differences in how different Intel NICs handle maximum
                    packet length for jumbo frame
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: nandinipersad361@gmail.com
  Target Milestone: ---

10 Gigabit Ethernet devices from Intel do not take VLAN tags into account when
calculating packet size while Gigabit Ethernet devices do so for jumbo frames.

Implication:
When receiving packets with VLAN tags, the actual maximum size of useful
payload that Intel Gigabit Ethernet devices are able to receive is 4 bytes (or
8 bytes in the case of packets with extended VLAN tags) less than that of Intel
10 Gigabit Ethernet devices.

Resolution/Workaround:
Increase the configured maximum packet size when using Intel Gigabit Ethernet
devices.

Affected Environment/Platform:
All.

Driver/Module:
Poll Mode Driver (PMD).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3142 bytes --]

                 reply	other threads:[~2025-02-03  3:05 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-1638-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.