From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Kathleen Capella <kathleen.capella@arm.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "nd@arm.com" <nd@arm.com>,
"honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>,
"joyce.kong@arm.com" <joyce.kong@arm.com>
Subject: RE: [PATCH] net/iavf: replace SMP barrier with thread fence
Date: Sun, 13 Mar 2022 12:15:26 +0000 [thread overview]
Message-ID: <6499b2c4a8d24df6868880d5e0b6a817@intel.com> (raw)
In-Reply-To: <20220307192644.31721-1-kathleen.capella@arm.com>
> -----Original Message-----
> From: Kathleen Capella <kathleen.capella@arm.com>
> Sent: Tuesday, March 8, 2022 3:27 AM
> To: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org; nd@arm.com; honnappa.nagarahalli@arm.com;
> joyce.kong@arm.com; Kathleen Capella <kathleen.capella@arm.com>
> Subject: [PATCH] net/iavf: replace SMP barrier with thread fence
>
> Replace the SMP barrier with atomic thread fence for iavf hw ring scan in the
> bulk Rx path.
>
> This patch introduces a change to the iavf driver that was already added to the
> i40e driver [1] as part of the adoption of the use of compiler atomics.
>
> [1] https://patches.dpdk.org/project/dpdk/patch/20210706065404.25137-3-
> joyce.kong@arm.com/
Better replace URL with below commit line
Commit 8649e2356689 ("net/i40e: replace SMP barrier with thread fence in Rx")
Btw, the patch will be deferred to the next release as it's not a critical fix.
next prev parent reply other threads:[~2022-03-13 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 19:26 Kathleen Capella
2022-03-13 12:15 ` Zhang, Qi Z [this message]
2022-03-24 8:49 ` Zhang, Qi Z
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=6499b2c4a8d24df6868880d5e0b6a817@intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=jingjing.wu@intel.com \
--cc=joyce.kong@arm.com \
--cc=kathleen.capella@arm.com \
--cc=nd@arm.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).