All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1666] It is not possible to increase the MTU for AF_PACKET PMD beyond 1500B
Date: Fri, 28 Feb 2025 12:03:48 +0000	[thread overview]
Message-ID: <bug-1666-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1666
           Summary: It is not possible to increase the MTU for AF_PACKET
                    PMD beyond 1500B
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: angelo.mirabella96@gmail.com
  Target Milestone: ---

Created attachment 302
  --> https://bugs.dpdk.org/attachment.cgi?id=302&action=edit
testpmd logs

Hi everyone,

I'm currently working with DPDK v21.11 from the official Ubuntu Jammy package,
having recently upgraded from v19.11. I noticed that a new check,
"eth_dev_validate_mtu", has been introduced in "eth_dev_configure".

The final check in this function is:


```
        if (frame_size > dev_info->max_rx_pktlen) {
---
```

For the AF_PACKET PMD, "max_rx_pktlen" is hardcoded to RTE_ETHER_MAX_LEN
(1518). As a result, any attempt to increase the MTU beyond 1500 fails, even
when the vdev is configured with a larger framesz.

I've attached logs from testpmd for reference. Any insights or possible
workarounds would be appreciated!

Thanks!

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

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

                 reply	other threads:[~2025-02-28 12:03 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-1666-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.