From: Ferruh Yigit <ferruh.yigit@intel.com>
To: <yongwang@vmware.com>
Cc: <dev@dpdk.org>, <sahithi.singam@oracle.com>
Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: add spinlocks to register command access
Date: Tue, 16 Nov 2021 17:16:03 +0000 [thread overview]
Message-ID: <78787fb2-aa55-426a-1bff-29515acec9dc@intel.com> (raw)
In-Reply-To: <20211108082331.1407-1-sahithi.singam@oracle.com>
On 11/8/2021 8:23 AM, sahithi.singam@oracle.com wrote:
> From: Sahithi Singam<sahithi.singam@oracle.com>
>
> At present, there are no spinlocks around register command access.
> This resulted in a race condition when two threads running on
> two different cores invoked link_update function at the same time
> to get link status. Due to this race condition, one of the threads
> reported false link status value.
>
> Signed-off-by: Sahithi Singam<sahithi.singam@oracle.com>
Hi Yong, can you please review this patch?
next prev parent reply other threads:[~2021-11-16 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 8:23 sahithi.singam
2021-11-16 17:16 ` Ferruh Yigit [this message]
2021-11-30 7:31 ` Yong Wang
2021-11-30 8:58 ` 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=78787fb2-aa55-426a-1bff-29515acec9dc@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=sahithi.singam@oracle.com \
--cc=yongwang@vmware.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).