DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 961] PCAP PMD receives packets larger then MTU
Date: Tue, 04 Jul 2023 17:43:09 +0000	[thread overview]
Message-ID: <bug-961-3-V9jkQ77Z3k@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-961-3@http.bugs.dpdk.org/>

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

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

Stephen Hemminger (stephen@networkplumber.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stephen@networkplumber.org
         Resolution|---                         |WONTFIX
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #4 from Stephen Hemminger (stephen@networkplumber.org) ---
This is not a bug. Other drivers allow bigger frames.

It is part of the overall confusion of what does MTU mean in OS.
In Linux and FreeBSD, it is maximum transmission unit and it also
serves as the minimum receive unit for device drivers.

Many device drivers will receive oversize packets, and leave it up to upper
layers to handle. It is the device driver version of the robustness principle
(aka Postel's Law).

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

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

      reply	other threads:[~2023-07-04 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 13:53 bugzilla
2023-07-04 17:43 ` bugzilla [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=bug-961-3-V9jkQ77Z3k@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).