From: Bruce Richardson <bruce.richardson@intel.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: <dev@dpdk.org>, Praveen Shetty <praveen.shetty@intel.com>,
"Vladimir Medvedkin" <vladimir.medvedkin@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>
Subject: Re: [PATCH] net/intel: improve Rx descriptor ring size checks
Date: Mon, 15 Dec 2025 17:58:33 +0000 [thread overview]
Message-ID: <aUBMSa4u2Qjyy4t3@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F655E6@smartserver.smartshare.dk>
On Mon, Dec 15, 2025 at 06:54:50PM +0100, Morten Brørup wrote:
> > From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> > Sent: Monday, 15 December 2025 18.36
> >
> > The default Rx ring size checks did not account for the fact that the
> > port would not work correctly if the Rx ring size was only twice the
> > free threshold size or less, so add in a new check for this. This would
> > generally only apply in cases where very small rings sizes are being
> > used, for example, with default Rx free thresh of 32, only ring size of
> > 64 would cause issues.
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > ---
>
> Does dev_info.rx_desc_lim.nb_min returned by rte_eth_dev_info_get() need correction too?
>
The minimum number of descriptors stays the same, however, if choosing the
minimum number of descriptors you may need to reduce the rx_free_thresh
value.
/Bruce
next prev parent reply other threads:[~2025-12-15 17:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 17:35 Bruce Richardson
2025-12-15 17:54 ` Morten Brørup
2025-12-15 17:58 ` Bruce Richardson [this message]
2025-12-15 18:20 ` Bruce Richardson
2025-12-15 18:53 ` Morten Brørup
2025-12-16 8:48 ` Bruce Richardson
2025-12-16 9:25 ` Morten Brørup
2025-12-16 9:52 ` Bruce Richardson
2025-12-16 10:48 ` Morten Brørup
2025-12-15 18:43 ` [PATCH v2] " Bruce Richardson
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=aUBMSa4u2Qjyy4t3@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=mb@smartsharesystems.com \
--cc=praveen.shetty@intel.com \
--cc=vladimir.medvedkin@intel.com \
/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).