From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [net/mlx5] Performance drop with HWS compared to SWS
Date: Fri, 27 Sep 2024 14:33:03 +0300 [thread overview]
Message-ID: <20240927143303.4860f34a@sovereign> (raw)
In-Reply-To: <PH0PR12MB880055029212CFDAEB0728C2A4CF2@PH0PR12MB8800.namprd12.prod.outlook.com>
2024-06-19 19:15 (UTC+0000), Dariusz Sosnowski:
[...]
> We're still looking into "jump_drop" case.
Hi Dariusz, any update?
P.S. Thanks for the talk at DPDK Summit, looking forward for more like it.
Debugging HW features is tricky and shedding light is much appreciated.
next prev parent reply other threads:[~2024-09-27 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 9:01 Dmitry Kozlyuk
2024-06-13 15:06 ` Dariusz Sosnowski
2024-06-13 20:14 ` Dmitry Kozlyuk
2024-06-19 19:15 ` Dariusz Sosnowski
2024-06-20 13:05 ` Dmitry Kozlyuk
2024-09-27 11:33 ` Dmitry Kozlyuk [this message]
2024-10-09 17:16 ` 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=20240927143303.4860f34a@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=dsosnowski@nvidia.com \
--cc=users@dpdk.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).