From: David Marchand <david.marchand@redhat.com>
To: Jingjing Wu <jingjing.wu@intel.com>, Beilei Xing <beilei.xing@intel.com>
Cc: dev@dpdk.org, qi.z.zhang@intel.com, thomas@monjalon.net,
yidingx.zhou@intel.com, ktraynor@redhat.com, stable@dpdk.org,
Mike Pattrick <mkp@redhat.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [PATCH v4] net/iavf: add lock for vf commands
Date: Fri, 13 Jan 2023 14:35:29 +0100 [thread overview]
Message-ID: <CAJFAV8w3pv6TW6mSmnYsaow56MgNAoEsOczXUOeFn4Xc5iTGfQ@mail.gmail.com> (raw)
In-Reply-To: <20221228230025.1430743-1-mkp@redhat.com>
Hi iavf maintainers,
On Thu, Dec 29, 2022 at 12:00 AM Mike Pattrick <mkp@redhat.com> wrote:
>
> iavf admin queue commands aren't thread-safe. Bugs surrounding this
> issue can manifest in a variety of ways but frequently pend_cmd is
> over written. Simultaneously executing commands can result in a
> misconfigured device or DPDK sleeping in a thread for 2 second.
>
> Despite this limitation, vf commands may be executed from both
> iavf_dev_alarm_handler() in a control thread and the applications main
> thread. This is trivial to simulate in the testpmd application by
> creating a bond of vf's in active backup mode, and then turning the
> bond off and then on again repeatedly.
>
> Previously [1] was proposed as a potential solution, but this commit did
> not resolve all potential issues concerning the admin queue and has been
> reverted from the stable branch. I propose adding locks until a more
> complete solution is available.
>
> [1] commit cb5c1b91f76f ("net/iavf: add thread for event callbacks")
>
> Fixes: 48de41ca11f0 ("net/avf: enable link status update")
> Fixes: 84108425054a ("net/iavf: support asynchronous virtual channel message")
> Cc: stable@dpdk.org
>
> Signed-off-by: Mike Pattrick <mkp@redhat.com>
Review please.
--
David Marchand
next prev parent reply other threads:[~2023-01-13 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 23:23 [PATCH] " Mike Pattrick
2022-12-20 15:02 ` David Marchand
2022-12-20 15:54 ` [PATCH v2] " Mike Pattrick
2022-12-26 6:01 ` Zhang, Qi Z
2022-12-28 22:28 ` [PATCH v3] " Mike Pattrick
2022-12-28 23:00 ` [PATCH v4] " Mike Pattrick
2023-01-13 13:35 ` David Marchand [this message]
2023-01-17 1:20 ` 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=CAJFAV8w3pv6TW6mSmnYsaow56MgNAoEsOczXUOeFn4Xc5iTGfQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=mkp@redhat.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yidingx.zhou@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).