DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Adrian Schollmeyer <a.schollmeyer@syseleven.de>
Cc: dev@dpdk.org, Michael Rossberg <michael.rossberg@tu-ilmenau.de>,
	Erez Ferber <erezf@nvidia.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: Re: [PATCH] net/mlx5: store rxq MTU at allocation time
Date: Wed, 05 Nov 2025 16:22:13 +0100	[thread overview]
Message-ID: <2962335.1SvkZsmPdQ@thomas> (raw)
In-Reply-To: <20251028095240.35281-1-a.schollmeyer@syseleven.de>

Hello,

I don't find this patch in patchwork.
Please could you try sending it again?
Please use --cc-cmd devtools/get-maintainer.sh
to make sure the maintainers are in Cc.

Thanks


28/10/2025 10:52, a.schollmeyer@syseleven.de:
> From: Adrian Schollmeyer <a.schollmeyer@syseleven.de>
> 
> For shared Rx queues, equal MTU for all ports sharing queues is enforced
> using mlx5_shared_rxq_match() to make sure, the memory allocated in the
> Rx buffer is large enough. The check uses the MTU as reported by the
> ports' private dev_data structs, which contain the MTU currently set for
> the device. In case one port's MTU is altered after Rx queues are
> allocated and then a second port joins the shared Rx queue with the old,
> yet correct MTU, the check fails despite the fact that the Rx buffer
> size is correct for both ports.
> 
> This patch adds a new entry to the Rx queue control structure that
> captures the MTU at the time the Rx buffer was allocated, since this is
> the relevant information that needs to be checked when a port joins a
> shared Rx queue.
> 
> Fixes: 09c2555303be





  reply	other threads:[~2025-11-05 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28  9:52 a.schollmeyer
2025-11-05 15:22 ` Thomas Monjalon [this message]
2025-11-05 15:34   ` Morten Brørup
     [not found] <20251028095502.1CFB21261CB@dpdk.org>
2025-10-28 10:01 ` a.schollmeyer
2025-10-28 10:40   ` Dariusz Sosnowski

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=2962335.1SvkZsmPdQ@thomas \
    --to=thomas@monjalon.net \
    --cc=a.schollmeyer@syseleven.de \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=erezf@nvidia.com \
    --cc=michael.rossberg@tu-ilmenau.de \
    /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).