From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Thierry Herbelot <thierry.herbelot@6wind.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Devendra Singh Rawat <dsinghrawat@marvell.com>,
Alok Prasad <palok@marvell.com>, Jerin Jacob <jerinj@marvell.com>,
Olivier Matz <olivier.matz@6wind.com>,
Edwin Brossette <edwin.brossette@6wind.com>,
stable@dpdk.org
Subject: Re: [V3] net/qede: reduce the optimization level for gcc > 11
Date: Tue, 16 Sep 2025 10:59:00 +0200 [thread overview]
Message-ID: <CAJFAV8ytULR3Gr21Y2kUCgOigGJuRiU7DWb7QZLNzWLhsXDVFA@mail.gmail.com> (raw)
In-Reply-To: <20250910090926.204ff85d@hermes.local>
On Wed, 10 Sept 2025 at 18:42, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> On Wed, 10 Sep 2025 08:49:38 +0200
> Thierry Herbelot <thierry.herbelot@6wind.com> wrote:
> > The error chain is:
> >
> > RX-nombufs
> > => (testpmd) stats.rx_nombuf
> > => (qede) p_stats->common.no_buff_discards
> > => (qede/base) HILO_64_REGPAIR(mstats.no_buff_discard)
> > (internal to the NIC)
> >
>
> Thanks, lets root cause this (rather than paper it over) because
+1
> other drivers may have same issue. Since no mbufs are present
> looks like rx discriptor never made it to NIC
I would add that if the descs do make it to the nic, maybe the (IOVA)
addresses are incorrect.
We changed the default IOVA not so long ago.. so maybe play with
--iova-mode to continue investigations.
--
David Marchand
prev parent reply other threads:[~2025-09-16 8:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 11:32 [PATCH] net/qede: reduce the optimization level Thierry Herbelot
2025-09-06 3:59 ` Stephen Hemminger
2025-09-08 7:04 ` [V2] net/qede: reduce the optimization level for gcc > 11 Thierry Herbelot
2025-09-08 19:59 ` Stephen Hemminger
2025-09-09 5:27 ` Thierry Herbelot
2025-09-09 5:40 ` [V3] " Thierry Herbelot
2025-09-09 16:17 ` Stephen Hemminger
2025-09-10 6:49 ` Thierry Herbelot
2025-09-10 16:09 ` Stephen Hemminger
2025-09-16 8:59 ` David Marchand [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=CAJFAV8ytULR3Gr21Y2kUCgOigGJuRiU7DWb7QZLNzWLhsXDVFA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dsinghrawat@marvell.com \
--cc=edwin.brossette@6wind.com \
--cc=jerinj@marvell.com \
--cc=olivier.matz@6wind.com \
--cc=palok@marvell.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thierry.herbelot@6wind.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).