All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: lulu@redhat.com, tiwei.bie@intel.com, jasowang@redhat.com,
	qemu-devel@nongnu.org, raphael.norwitz@nutanix.com,
	maxime.coquelin@redhat.com, kraxel@redhat.com,
	Felipe Franciosi <felipe@nutanix.com>,
	marcandre.lureau@redhat.com,
	Nikos Dragazis <ndragazis@arrikto.com>,
	changpeng.liu@intel.com, Daniele Buono <dbuono@us.ibm.com>
Subject: Re: Outline for VHOST_USER_PROTOCOL_F_VDPA
Date: Wed, 30 Sep 2020 11:34:12 -0400	[thread overview]
Message-ID: <20200930113129-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200930145752.GB320669@stefanha-x1.localdomain>

On Wed, Sep 30, 2020 at 03:57:52PM +0100, Stefan Hajnoczi wrote:
> > Architecturally, I think we can have 3 processes:
> > 
> > 
> > VMM -- guest device emulation -- host backend
> > 
> > 
> > to me this looks like increasing our defence in depth strength,
> > as opposed to just shifting things around ...
> 
> Cool idea.
> 
> Performance will be hard because there is separation between the guest
> device emulation and the host backend.

Absolutely. As a tradeoff we could put some data path things in the backend,
e.g. for virtio it is practical to have control path in emulation layer,
data path in the backend.

-- 
MST



  parent reply	other threads:[~2020-09-30 15:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28  9:25 Outline for VHOST_USER_PROTOCOL_F_VDPA Stefan Hajnoczi
2020-09-28 11:21 ` Marc-André Lureau
2020-09-28 15:32   ` Stefan Hajnoczi
2020-10-12  2:56     ` Jason Wang
2020-09-29  6:09 ` Michael S. Tsirkin
2020-09-29  8:57   ` Stefan Hajnoczi
2020-09-29 10:04     ` Michael S. Tsirkin
2020-09-29 18:38       ` Stefan Hajnoczi
2020-09-30  8:07         ` Michael S. Tsirkin
2020-09-30 14:57           ` Stefan Hajnoczi
2020-09-30 15:31             ` Michael S. Tsirkin
2020-09-30 15:34             ` Michael S. Tsirkin [this message]
2020-10-01  7:28             ` Gerd Hoffmann
2020-10-01 15:13               ` Stefan Hajnoczi
2020-10-12  3:52           ` Jason Wang

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=20200930113129-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=changpeng.liu@intel.com \
    --cc=dbuono@us.ibm.com \
    --cc=felipe@nutanix.com \
    --cc=jasowang@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lulu@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=ndragazis@arrikto.com \
    --cc=qemu-devel@nongnu.org \
    --cc=raphael.norwitz@nutanix.com \
    --cc=stefanha@redhat.com \
    --cc=tiwei.bie@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.