From: Thomas Monjalon <thomas@monjalon.net>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"matan@mellanox.com" <matan@mellanox.com>,
"Zawadzki, Tomasz" <tomasz.zawadzki@intel.com>,
"Liu, Changpeng" <changpeng.liu@intel.com>,
"Xia, Chenbo" <chenbo.xia@intel.com>
Subject: Re: [dpdk-dev] [PATCH] vhost: fix external backends readiness
Date: Mon, 28 Sep 2020 17:19:57 +0200 [thread overview]
Message-ID: <10016219.ukWWe7AENh@thomas> (raw)
In-Reply-To: <BY5PR11MB4055511447515CAF7E30B9909C350@BY5PR11MB4055.namprd11.prod.outlook.com>
28/09/2020 12:55, Xia, Chenbo:
> >
> > Commit d0fcc38f5fa4 ("vhost: improve device readiness notifications")
> > makes the assumption that every Virtio devices are considered
> > ready for preocessing as soon as first queue pair is configured
> > and enabled.
> >
> > While this is true for Virtio-net, it isn't for Virtio-scsi
> > and Virtio-blk.
> >
> > This patch fixes this by only making this assumption for
> > the builtin Virtio-net backend, and restores back to previous
> > behaviour for other backends.
> >
> > Fixes: d0fcc38f5fa4 ("vhost: improve device readiness notifications")
> >
> > Reported-by: Changpeng Liu <changpeng.liu@intel.com>
> > Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> > Signed-off-by: Changpeng Liu <changpeng.liu@intel.com>
>
> Reviewed-by: Chenbo Xia <chenbo.xia@intel.com>
Applied in the main repository, thanks.
prev parent reply other threads:[~2020-09-28 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 9:49 [dpdk-dev] [PATCH] vhost: fix external backends readiness Maxime Coquelin
2020-09-28 10:55 ` Xia, Chenbo
2020-09-28 15:19 ` Thomas Monjalon [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=10016219.ukWWe7AENh@thomas \
--to=thomas@monjalon.net \
--cc=changpeng.liu@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=maxime.coquelin@redhat.com \
--cc=tomasz.zawadzki@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.