From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Matan Azrad <matan@mellanox.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, chenbo.xia@intel.com, david.marchand@redhat.com,
thomas@monjalon.net, Marvin Liu <yong.liu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/vhost: support queue update
Date: Tue, 21 Jul 2020 18:25:14 +0100 [thread overview]
Message-ID: <87f4dd1f-0882-1dc3-0804-588ab7eb407e@intel.com> (raw)
In-Reply-To: <20200721163816.15057-1-matan@mellanox.com>
On 7/21/2020 5:38 PM, Matan Azrad wrote:
> The commit below changed the readiness condition of vhost device to fix
> multi-queues issues showed with QEMU versions.
>
> Now, the vhost device is ready when the first queue-pair is ready.
> When more queues are being ready, the queue state callback will be
> triggered to notify the vhost manager.
>
> In case of Rx interrupt configuration, the vhost driver set the
> kickfd queue file descriptor in order to be notified on Rx traffic.
>
> So, when queue becomes ready, the kickfd may be changed and should be
> updated in the Rx interrupt structure.
>
> Update kickfd when the queue state callback is invoked.
> Also update event notification when it is enabled by the user.
>
> Fixes: d0fcc38f5fa4 ("vhost: improve device readiness notifications")
>
> Signed-off-by: Matan Azrad <matan@mellanox.com>
Suggested-by: Marvin Liu <yong.liu@intel.com>
This patch addresses a ~%20 performance drop in vhost reported with -rc1.
Although it is missing component maintainers ack, I will merge it relying on
offline discussion Maxime, Matan, Marvin & Chenbo involved, to address the
performance issue observed in -rc2.
Hopefully won't but if we observe issues with this patch, there will be time to
address it before -rc3, I believe it is safer/better to merge it for -rc2 than
holding this fix till -rc3, at least it can be verified this way as part of -rc2.
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2020-07-21 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 16:18 [dpdk-dev] [PATCH v1] net/vhost: support queue update Matan Azrad
2020-07-21 16:38 ` [dpdk-dev] [PATCH v2] " Matan Azrad
2020-07-21 17:25 ` Ferruh Yigit [this message]
2020-07-21 17:27 ` Maxime Coquelin
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=87f4dd1f-0882-1dc3-0804-588ab7eb407e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=chenbo.xia@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.net \
--cc=yong.liu@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.