From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wu, Wenjun1" <wenjun1.wu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Su, Simei" <simei.su@intel.com>
Cc: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: RE: [PATCH v4] net/iavf: fix race condition for multi-cores
Date: Mon, 23 May 2022 05:17:38 +0000 [thread overview]
Message-ID: <DM4PR11MB5994E15E2B7EC485C881DB19D7D49@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220523044900.1437947-1-wenjun1.wu@intel.com>
> -----Original Message-----
> From: Wu, Wenjun1 <wenjun1.wu@intel.com>
> Sent: Monday, May 23, 2022 12:49 PM
> To: dev@dpdk.org; Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Su, Simei
> <simei.su@intel.com>
> Cc: stephen@networkplumber.org; Wu, Wenjun1 <wenjun1.wu@intel.com>
> Subject: [PATCH v4] net/iavf: fix race condition for multi-cores
>
> In multi-cores cases for RX timestamp offload, if packets arrive too fast, aq
> command to get phc time will be pended.
>
> This patch adds spinlock to fix this issue. To avoid phc time being frequently
> overwritten, move related variables to iavf_rx_queue structure, and each
> queue will handle timestamp calculation by itself.
>
> Fixes: 2a0a62f40af5 ("net/iavf: enable Rx timestamp on Flex Descriptor")
> Fixes: 33db16136e55 ("net/iavf: improve performance of Rx timestamp
> offload")
>
> Signed-off-by: Wenjun Wu <wenjun1.wu@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2022-05-23 5:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 1:19 [PATCH v1] " Wenjun Wu
2022-05-19 3:13 ` Stephen Hemminger
2022-05-19 7:33 ` [PATCH v2] " Wenjun Wu
2022-05-19 15:27 ` Stephen Hemminger
2022-05-20 7:35 ` [PATCH v3] " Wenjun Wu
2022-05-23 4:49 ` [PATCH v4] " Wenjun Wu
2022-05-23 5:17 ` Zhang, Qi Z [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=DM4PR11MB5994E15E2B7EC485C881DB19D7D49@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=simei.su@intel.com \
--cc=stephen@networkplumber.org \
--cc=wenjun1.wu@intel.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).