From: Thierry Herbelot <thierry.herbelot@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Olivier Matz <olivier.matz@6wind.com>,
dsinghrawat@marvell.com, palok@marvell.com, jerinj@marvell.com,
Laurent Hardy <laurent.hardy@6wind.com>,
Edwin Brossette <edwin.brossette@6wind.com>
Subject: Re: [RESEND] net/qede: workaround for operation in Ubuntu-24.04
Date: Thu, 28 Aug 2025 16:55:11 +0200 [thread overview]
Message-ID: <c2e83bd1-4a5f-447c-8ee5-261a0f886349@6wind.com> (raw)
In-Reply-To: <20250828075135.77381013@hermes.local>
On 8/28/25 16:51, Stephen Hemminger wrote:
> On Thu, 28 Aug 2025 10:09:35 +0200
> Thierry Herbelot <thierry.herbelot@6wind.com> wrote:
>
>> Hello,
>>
>> [resend because the original diff was for the 24.11 branch]
>>
>> qede stopped working with recent distributions, as explained in this bug
>> report:
>> https://bugs.dpdk.org/show_bug.cgi?id=1379
>>
>> For reference, one workaround is to disable all optimizations when
>> compiling the qede PMD with gcc-13, as seen in main branch:
>
>
> Using O0 is pretty drastic and can have bad performance and doing it for
> every distro will cause performance drop.
Hello Stephen
I absolutely agree: -O0 brings a big performance drop.
I am investigating if the qede PMD compiled with -O1 or -O2 optimization
levels and gcc-13 is still working.
Regards
Thierry
>
> All patches must have Signed-off-by, so this patch will be dropped.
--
Thierry Herbelot
prev parent reply other threads:[~2025-08-28 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 8:09 Thierry Herbelot
2025-08-28 14:51 ` Stephen Hemminger
2025-08-28 14:55 ` Thierry Herbelot [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=c2e83bd1-4a5f-447c-8ee5-261a0f886349@6wind.com \
--to=thierry.herbelot@6wind.com \
--cc=dev@dpdk.org \
--cc=dsinghrawat@marvell.com \
--cc=edwin.brossette@6wind.com \
--cc=jerinj@marvell.com \
--cc=laurent.hardy@6wind.com \
--cc=olivier.matz@6wind.com \
--cc=palok@marvell.com \
--cc=stephen@networkplumber.org \
/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).