From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: Joshua Washington <joshwash@google.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Hyong Youb Kim <hyonkim@cisco.com>, Rosen Xu <rosen.xu@intel.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Huisong Li <lihuisong@huawei.com>,
dev@dpdk.org, Rushil Gupta <rushilg@google.com>
Subject: Re: [PATCH v2] ethdev: account for smaller MTU when setting default
Date: Wed, 8 Nov 2023 09:05:35 -0800 [thread overview]
Message-ID: <CACZ4nhtJaNHfVFBtzzOsQNy6NhOYqY22XvbWC0pPpEW9SpVAKg@mail.gmail.com> (raw)
In-Reply-To: <e93848be-91a3-4e3f-9aa0-75fa30d320f7@oktetlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
On Wed, Nov 8, 2023 at 7:07 AM Andrew Rybchenko
<andrew.rybchenko@oktetlabs.ru> wrote:
>
> On 11/8/23 09:05, Joshua Washington wrote:
> > Currently, if not specified in the user configuration,
> > rte_eth_dev_configure() sets the MTU of the device to RTE_EHTER_MTU.
> > This value could potentially be larger than the MTU that the device
> > supports. This change updates the configured MTU to be the minimum of
> > the maximum suported MTU and the default DPDK MTU.
> >
> > Fixes: 1bb4a528c4 ("ethdev: fix max Rx packet length")
> > Signed-off-by: Joshua Washington <joshwash@google.com>
> > Signed-off-by: Rushil Gupta <rushilg@google.com>
>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
>
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
next prev parent reply other threads:[~2023-11-08 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 6:05 Joshua Washington
2023-11-08 15:07 ` Andrew Rybchenko
2023-11-08 17:05 ` Ajit Khaparde [this message]
2023-11-08 17:23 ` Ferruh Yigit
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=CACZ4nhtJaNHfVFBtzzOsQNy6NhOYqY22XvbWC0pPpEW9SpVAKg@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=hyonkim@cisco.com \
--cc=joshwash@google.com \
--cc=lihuisong@huawei.com \
--cc=rosen.xu@intel.com \
--cc=rushilg@google.com \
--cc=somnath.kotur@broadcom.com \
--cc=thomas@monjalon.net \
/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).