From: Tiwei Bie <tiwei.bie@intel.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: mst@redhat.com, jasowang@redhat.com, peterx@redhat.com,
qemu-devel@nongnu.org, dan.daly@intel.com,
cunming.liang@intel.com, zhihong.wang@intel.com
Subject: Re: [Qemu-devel] [RFC] vhost-user: introduce F_NEED_ALL_IOTLB protocol feature
Date: Tue, 17 Apr 2018 10:35:39 +0800 [thread overview]
Message-ID: <20180417023539.yweapei6mpvuqxhf@debian> (raw)
In-Reply-To: <20180416074706.GB28904@stefanha-x1.localdomain>
On Mon, Apr 16, 2018 at 03:47:06PM +0800, Stefan Hajnoczi wrote:
> On Wed, Apr 11, 2018 at 03:20:27PM +0800, Tiwei Bie wrote:
> > This patch introduces VHOST_USER_PROTOCOL_F_NEED_ALL_IOTLB
>
> Naming suggestion: "PREFILL_IOTLB" instead of "NEED_ALL_IOTLB".
>
> I wasn't able to guess what "NEED_ALL_IOTLB" does. "PREFILL_IOTLB"
> communicates that memory translation will be set up in advance.
By naming it as NEED_ALL_IOTLB, I want to indicate that,
without this, it's hard or impossible for backend to get
all the IOTLBs (because backend needs to meet IOVAs first
before getting the corresponding IOTLBs, and backend can't
tell whether it has met all the IOVAs or not, especially
when dynamic mapping is being used by guest). But with
this feature negotiated, backend will expect to get all
the IOTLBs. But it seems that, the name (NEED_ALL_IOTLB)
isn't good. And thanks for your suggestion! :)
Best regards,
Tiwei Bie
prev parent reply other threads:[~2018-04-17 2:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 7:20 [Qemu-devel] [RFC] vhost-user: introduce F_NEED_ALL_IOTLB protocol feature Tiwei Bie
2018-04-11 8:00 ` Peter Xu
2018-04-11 8:25 ` Tiwei Bie
2018-04-11 8:37 ` Peter Xu
2018-04-11 8:55 ` Tiwei Bie
2018-04-11 9:16 ` Peter Xu
2018-04-11 9:25 ` Tiwei Bie
2018-04-11 8:01 ` Jason Wang
2018-04-11 8:38 ` Tiwei Bie
2018-04-11 13:41 ` Jason Wang
2018-04-11 17:00 ` Michael S. Tsirkin
2018-04-12 3:23 ` Jason Wang
2018-04-12 3:37 ` Michael S. Tsirkin
2018-04-12 3:56 ` Jason Wang
2018-04-11 17:37 ` Michael S. Tsirkin
2018-04-12 1:44 ` Tiwei Bie
2018-04-12 7:38 ` Jason Wang
2018-04-12 8:10 ` Tiwei Bie
2018-04-12 9:40 ` Jason Wang
2018-04-11 13:22 ` Michael S. Tsirkin
2018-04-11 13:42 ` Jason Wang
2018-04-12 1:10 ` Tiwei Bie
2018-04-12 1:29 ` Michael S. Tsirkin
2018-04-12 1:39 ` Tiwei Bie
2018-04-12 1:57 ` Michael S. Tsirkin
2018-04-12 2:35 ` Tiwei Bie
2018-04-12 3:20 ` Michael S. Tsirkin
2018-04-12 3:35 ` Michael S. Tsirkin
2018-04-12 3:43 ` Jason Wang
2018-04-12 4:19 ` Michael S. Tsirkin
2018-04-12 3:37 ` Jason Wang
2018-04-12 3:41 ` Michael S. Tsirkin
2018-04-12 7:24 ` Jason Wang
2018-04-16 7:47 ` Stefan Hajnoczi
2018-04-17 2:14 ` Jason Wang
2018-04-17 2:35 ` Tiwei Bie [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=20180417023539.yweapei6mpvuqxhf@debian \
--to=tiwei.bie@intel.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=zhihong.wang@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).