From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Joyce Kong <joyce.kong@arm.com>, <jgrajcia@cisco.com>,
<stephen@networkplumber.org>
Cc: <dev@dpdk.org>, <nd@arm.com>, Ruifeng Wang <ruifeng.wang@arm.com>
Subject: Re: [PATCH v4 0/2] add a fast path for memif Rx/Tx
Date: Thu, 22 Sep 2022 10:12:39 +0100 [thread overview]
Message-ID: <28278beb-5a21-5ec3-1fdf-d2eb7db72f87@amd.com> (raw)
In-Reply-To: <20220915065825.26169-1-joyce.kong@arm.com>
On 9/15/2022 7:58 AM, Joyce Kong wrote:
> For memif non-zero-copy mode, there is a branch to compare
> the mbuf and memif buffer size during memory copy. Add a
> fast memcpy path by removing this branch with mbuf and memif
> buffer size defined at compile time. For Rx fast path, bulk
> allocating mbufs to get additional speedup. For Tx fast path,
> bulk free mbufs which come from the same mempool.
>
> When mbuf == memif buffer size, both Rx/Tx would choose the
> fast memcpy path. When mbuf < memif buffer size, the Rx
> chooses previous memcpy path while Tx chooses fast memcpy
> path. When mbuf > memif buffer size, the Rx chooses fast
> memcpy path while Tx chooses previous memcpy path.
>
> Test with 1p1q on N1SDP AArch64 server,
> ---------------------------------------------------------
> buf size | memif = mbuf | memif < mbuf | memif > mbuf
> ---------------------------------------------------------
> non-zc gain | 47.16% | 24.67% | 12.47%
> ---------------------------------------------------------
> zc gain | 20.96% | 9.16% | 10.66%
> ---------------------------------------------------------
>
> Test with 1p1q on Cascade Lake Xeon X86 server,
> ---------------------------------------------------------
> buf size | memif = mbuf | memif < mbuf | memif > mbuf
> ---------------------------------------------------------
> non-zc gain | 23.52% | 14.20% | 5.10%
> ---------------------------------------------------------
> zc gain | 17.49% | 10.62% | 12.42%
> ---------------------------------------------------------
>
> v4:
> 1.Fix incorrect indentation.
> 2.Fix the mbuf array length to avoid additional overhead if
> stack-protector strong is enabled. <Stephen Hemminger>
>
> v3:
> Add bulk allocation to get additional speedup for memif Rx
> fast path. <Stephen Hemminger>
>
> v2:
> Rebase v1 and update commit message.
>
> Joyce Kong (2):
> net/memif: add a Rx fast path
> net/memif: add a Tx fast path
>
Hi Jakub,
Reminder of this set waiting for your review.
Thanks,
ferruh
next prev parent reply other threads:[~2022-09-22 9:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 9:32 [RFC] net/memif: add a fast path for Rx Joyce Kong
2022-05-17 10:51 ` [PATCH v1 0/2] add a fast path for memif Rx/Tx Joyce Kong
2022-05-17 10:51 ` [PATCH v1 1/2] net/memif: add a Rx fast path Joyce Kong
2022-05-18 16:53 ` Ferruh Yigit
2022-05-19 7:00 ` Joyce Kong
2022-05-19 8:44 ` Joyce Kong
2022-05-18 17:06 ` Ferruh Yigit
2022-05-19 15:09 ` Joyce Kong
2022-05-19 16:38 ` Ferruh Yigit
2022-05-17 10:51 ` [PATCH v1 2/2] net/memif: add a Tx " Joyce Kong
2022-05-17 13:59 ` [PATCH v1 0/2] add a fast path for memif Rx/Tx Morten Brørup
2022-05-18 2:48 ` Ruifeng Wang
2022-07-01 10:28 ` [PATCH v2 " Joyce Kong
2022-07-01 10:28 ` [PATCH v2 1/2] net/memif: add a Rx fast path Joyce Kong
2022-07-01 16:51 ` Stephen Hemminger
2022-08-22 3:47 ` [PATCH v3 0/2] add a fast path for memif Rx/Tx Joyce Kong
2022-08-22 3:47 ` [PATCH v3 1/2] net/memif: add a Rx fast path Joyce Kong
2022-08-31 16:25 ` Stephen Hemminger
2022-09-07 6:06 ` Joyce Kong
2022-08-22 3:47 ` [PATCH v3 2/2] net/memif: add a Tx " Joyce Kong
2022-07-01 10:28 ` [PATCH v2 " Joyce Kong
2022-09-15 6:58 ` [PATCH v4 0/2] add a fast path for memif Rx/Tx Joyce Kong
2022-09-15 6:58 ` [PATCH v4 1/2] net/memif: add a Rx fast path Joyce Kong
2022-09-15 6:58 ` [PATCH v4 2/2] net/memif: add a Tx " Joyce Kong
2022-09-22 9:12 ` Ferruh Yigit [this message]
2022-12-09 13:59 ` [PATCH v4 0/2] add a fast path for memif Rx/Tx Ferruh Yigit
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=28278beb-5a21-5ec3-1fdf-d2eb7db72f87@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=joyce.kong@arm.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.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).