From: "Phil Yang (Arm Technology China)" <Phil.Yang@arm.com>
To: "Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco)"
<jgrajcia@cisco.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"jerinj@marvell.com" <jerinj@marvell.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"Damjan Marion (damarion)" <damarion@cisco.com>, nd <nd@arm.com>,
"Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v1] net/memif: optimized with one-way barrier
Date: Wed, 9 Oct 2019 02:10:49 +0000 [thread overview]
Message-ID: <VE1PR08MB46403AB4A9A76F71ECBB05C8E9950@VE1PR08MB4640.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <643c7eb281aa4b1e832f9d7f34af741f@XCH-ALN-004.cisco.com>
> -----Original Message-----
> From: Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco)
> <jgrajcia@cisco.com>
> Sent: Tuesday, October 8, 2019 7:05 PM
> To: Phil Yang (Arm Technology China) <Phil.Yang@arm.com>; dev@dpdk.org
> Cc: thomas@monjalon.net; jerinj@marvell.com; Honnappa Nagarahalli
> <Honnappa.Nagarahalli@arm.com>; Damjan Marion (damarion)
> <damarion@cisco.com>; nd <nd@arm.com>; Gavin Hu (Arm Technology
> China) <Gavin.Hu@arm.com>; nd <nd@arm.com>
> Subject: RE: [dpdk-dev] [PATCH v1] net/memif: optimized with one-way
> barrier
>
> > > -----Original Message-----
> > > From: dev <dev-bounces@dpdk.org> On Behalf Of Phil Yang
> > > Sent: Monday, August 26, 2019 7:00 PM
> > > To: jgrajcia@cisco.com; dev@dpdk.org
> > > Cc: thomas@monjalon.net; jerinj@marvell.com; Honnappa Nagarahalli
> > > <Honnappa.Nagarahalli@arm.com>; damarion@cisco.com; nd
> > <nd@arm.com>
> > > Subject: [dpdk-dev] [PATCH v1] net/memif: optimized with one-way
> > > barrier
> > >
> > > Using 'rte_mb' to synchronize the shared ring head/tail between
> > > producer and consumer will stall the pipeline and damage performance
> > > on the weak memory model platforms, such like aarch64. Meanwhile
> > > update the shared ring head and tail are observable and ordered
> between
> > CPUs on IA.
> > >
> > > Optimized this full barrier with the one-way barrier can improve the
> > > throughput. On aarch64 n1sdp server this patch make testpmd
> throughput
> > > boost 2.1%. On Intel E5-2640, testpmd got 3.98% performance gain.
> > >
> > > Signed-off-by: Phil Yang <phil.yang@arm.com>
> > > Reviewed-by: Gavin Hu <gavin.hu@arm.com>
>
> The patch is looking good, but 'MEMIF_VERSION_MAJOR' in memif.h needs
> to
> be set to 3 as ring pointers are no longer volatile.
Updated in v2.
Thanks for your comments.
Thanks,
Phil
next prev parent reply other threads:[~2019-10-09 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 11:00 Phil Yang
2019-08-26 11:03 ` Phil Yang (Arm Technology China)
2019-10-08 11:05 ` Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco)
2019-10-09 2:10 ` Phil Yang (Arm Technology China) [this message]
2019-10-09 11:17 ` Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco)
2019-10-14 8:59 ` Ferruh Yigit
2019-10-09 2:04 ` [dpdk-dev] [PATCH v2] " Phil Yang
2019-10-09 11:14 ` Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco)
2019-10-10 14:04 ` David Marchand
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=VE1PR08MB46403AB4A9A76F71ECBB05C8E9950@VE1PR08MB4640.eurprd08.prod.outlook.com \
--to=phil.yang@arm.com \
--cc=Gavin.Hu@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=damarion@cisco.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=jgrajcia@cisco.com \
--cc=nd@arm.com \
--cc=thomas@monjalon.net \
/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).