From: Stephen Hemminger <stephen@networkplumber.org>
To: Wei Hu <weh@microsoft.com>
Cc: dev@dpdk.org, ferruh.yigit@amd.com,
andrew.rybchenko@oktetlabs.ru, Long Li <longli@microsoft.com>,
stable@dpdk.org
Subject: Re: [PATCH 1/1] net/mana: do not ring short doorbell for every mbuf allocation
Date: Thu, 6 Feb 2025 17:22:58 -0800 [thread overview]
Message-ID: <20250206172258.20ca9bf3@hermes.local> (raw)
In-Reply-To: <20250206100744.734612-1-weh@microsoft.com>
On Thu, 6 Feb 2025 02:07:43 -0800
Wei Hu <weh@microsoft.com> wrote:
> In the 32bit rx path, it rings short doorbell after receiving
> one packet and alocating the new mbuf. This significantly
> impacets the rx performance. Fix this problem by ringing the
> short doorbell in batch.
>
> Fixes: eeb37809601b ("net/mana: use bulk mbuf allocation for Rx WQEs")
> Cc: stable@dpdk.org
>
> Signed-off-by: Wei Hu <weh@microsoft.com>
Applied to next-net with spelling fixes to the commit message.
prev parent reply other threads:[~2025-02-07 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 10:07 [PATCH 1/1] net/mana: do not ring short doorbell for every mbuf allocation Wei Hu
2025-02-07 1:22 ` Stephen Hemminger [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=20250206172258.20ca9bf3@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=longli@microsoft.com \
--cc=stable@dpdk.org \
--cc=weh@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.