From: 杨平 <yangping0081@gmail.com>
To: users@dpdk.org, chenbo.xia@intel.com, maxime.coquelin@redhat.com
Subject: Does dpdk vhost-user lib support VIRTIO_F_NOTIFY_ON_EMPTY？
Date: Thu, 28 Jul 2022 18:07:58 +0800 [thread overview]
Message-ID: <CAGUG4FeCG+E5iaSMQ2XskmcGfjNMgzv6JE6jCpnKu-=VaDaoiA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
Hi Maxime/Chenbo
We are using lib/librte_vhost to implement our virtio-backend devices.
Does DPDK vhost-user support VIRTIO_F_NOTIFY_ON_EMPTY, the legacy interface
reserved feature bit? (The 6.3 section in
https://stefanha.github.io/virtio/vhost-user-slave.html)
I'd see it set in VIRTIO_NET_SUPPORTED_FEATURES in vhost.h. So, will it
cause an exception if we migrate the VM which uses vhost_net and enable
VIRTIO_F_NOTIFY_ON_EMPTY?
Look forward to hearing from you.
Thanks
Ping Yang
[-- Attachment #2: Type: text/html, Size: 720 bytes --]
reply other threads:[~2022-08-11 8:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAGUG4FeCG+E5iaSMQ2XskmcGfjNMgzv6JE6jCpnKu-=VaDaoiA@mail.gmail.com' \
--to=yangping0081@gmail.com \
--cc=chenbo.xia@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=users@dpdk.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).