From: Rajasekhar Pulluru <pullururajasekhar@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: Restrict max packet size on rx
Date: Fri, 18 Oct 2024 22:19:35 +0530 [thread overview]
Message-ID: <CAGA5_H7a2D8SHUGhVZYKj_T9siRVMpxwJCSNS3fVZa3RMOzx0g@mail.gmail.com> (raw)
In-Reply-To: <20241018094348.4e91b6e5@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
Thanks Stephen.
On Fri, Oct 18, 2024 at 10:13 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Fri, 18 Oct 2024 22:05:24 +0530
> Rajasekhar Pulluru <pullururajasekhar@gmail.com> wrote:
>
> > Team,
> > Does setting mtu using rte_eth_dev_set_mtu limit the maximum size of the
> > packet received on the dpdk port to the configured mtu size?
> >
> > On an intel machine with ixgbe port, with mtu set to 1500, no rx-offloads
> > enabled, ixgbe dpdk port is able to receive packets greater than 1500
> size
> > and even jumbo frames of size 9000, even though the peer is sending them
> > fragmented with mtu of 1500.
> >
> > How do I restrict the port not to receive any frame greater than mtu
> size?
> >
> > Appreciate any help,
> > Thanks.
> > Rajasekhar
>
>
> In networking, MTU and MRU are overlapping concepts.
> The MTU value is used as a hint to the driver as to what size buffer to
> allocate
> but it can use larger if it wants. If you have restrictions, then the
> application
> needs to enforce them.
>
[-- Attachment #2: Type: text/html, Size: 1491 bytes --]
next prev parent reply other threads:[~2024-10-18 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 16:35 Rajasekhar Pulluru
2024-10-18 16:43 ` Stephen Hemminger
2024-10-18 16:49 ` Rajasekhar Pulluru [this message]
2024-10-18 17:37 ` Stephen Hemminger
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=CAGA5_H7a2D8SHUGhVZYKj_T9siRVMpxwJCSNS3fVZa3RMOzx0g@mail.gmail.com \
--to=pullururajasekhar@gmail.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).