DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: Joshua Washington <joshwash@google.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	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 17:23:09 +0000	[thread overview]
Message-ID: <4fc89af2-45e2-4588-9c3c-4e3c5833302b@amd.com> (raw)
In-Reply-To: <CACZ4nhtJaNHfVFBtzzOsQNy6NhOYqY22XvbWC0pPpEW9SpVAKg@mail.gmail.com>

On 11/8/2023 5:05 PM, Ajit Khaparde wrote:
> 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>
> 

Applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2023-11-08 17:23 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
2023-11-08 17:23     ` Ferruh Yigit [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=4fc89af2-45e2-4588-9c3c-4e3c5833302b@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --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).