From: Luca Boccassi <bluca@debian.org>
To: Long Li <longli@linuxonhyperv.com>, stable@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Long Li <longli@microsoft.com>
Subject: Re: [dpdk-stable] [PATCH 19.11] net/netvsc: manage VF port under read/write lock
Date: Thu, 17 Dec 2020 09:28:10 +0000 [thread overview]
Message-ID: <528a5ce07a4b2b96100934e64ff7e4254b8f3866.camel@debian.org> (raw)
In-Reply-To: <1608087878-7407-1-git-send-email-longli@linuxonhyperv.com>
On Tue, 2020-12-15 at 19:04 -0800, Long Li wrote:
> From: Stephen Hemminger <stephen@networkplumber.org>
>
> [ upstream commit 81938ebb542f1ce19254f58705583a7f48a95216 ]
>
> With multiple channels, the primary channel may receive notification
> that VF has been added or removed while secondary channel is in
> process of doing receive or transmit. Resolve this race by converting
> existing vf_lock to a reader/writer lock.
>
> Users of lock (tx/rx/stats) acquire for read, and actions like
> add/remove acquire it for write.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Signed-off-by: Long Li <longli@microsoft.com>
> ---
> drivers/net/netvsc/hn_ethdev.c | 2 +-
> drivers/net/netvsc/hn_rxtx.c | 8 ++-
> drivers/net/netvsc/hn_var.h | 10 ++--
> drivers/net/netvsc/hn_vf.c | 99 ++++++++++++++++------------------
> 4 files changed, 59 insertions(+), 60 deletions(-)
Thank you, applied.
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2020-12-17 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 3:04 Long Li
2020-12-17 9:28 ` Luca Boccassi [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=528a5ce07a4b2b96100934e64ff7e4254b8f3866.camel@debian.org \
--to=bluca@debian.org \
--cc=longli@linuxonhyperv.com \
--cc=longli@microsoft.com \
--cc=stable@dpdk.org \
--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).