From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: Somnath Kotur <somnath.kotur@broadcom.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] net/bnxt: support fast mbuf free
Date: Tue, 6 Oct 2020 14:26:28 -0700 [thread overview]
Message-ID: <CACZ4nhv3myj31Ef5JTO4FvVNq4Ye-7YmUchia-eVgOYqG8rG8A@mail.gmail.com> (raw)
In-Reply-To: <20201006173752.104002-1-lance.richardson@broadcom.com>
On Tue, Oct 6, 2020 at 10:37 AM Lance Richardson
<lance.richardson@broadcom.com> wrote:
>
> Add support for DEV_TX_OFFLOAD_MBUF_FAST_FREE to bnxt
> vector mode transmit. This offload may be enabled
> only when multi-segment transmit is not needed, all
> transmitted mbufs for a given queue will be allocated
> from the same pool, and all transmitted mbufs will
> have a reference count of 1.
>
> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
Patch applied to dpdk-next-net-brcm. Thanks
prev parent reply other threads:[~2020-10-06 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 13:40 [dpdk-dev] [PATCH v2] " Lance Richardson
2020-10-06 17:37 ` [dpdk-dev] [PATCH v3] " Lance Richardson
2020-10-06 21:26 ` Ajit Khaparde [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=CACZ4nhv3myj31Ef5JTO4FvVNq4Ye-7YmUchia-eVgOYqG8rG8A@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=lance.richardson@broadcom.com \
--cc=somnath.kotur@broadcom.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).