Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
	virtio-dev@lists.oasis-open.org, hans@linux.alibaba.com,
	herongguang@linux.alibaba.com, zmlcc@linux.alibaba.com,
	dust.li@linux.alibaba.com, tonylu@linux.alibaba.com,
	zhenzao@linux.alibaba.com, helinguo@linux.alibaba.com,
	gerry@linux.alibaba.com, cohuck@redhat.com,
	Jan Kiszka <jan.kiszka@siemens.com>,
	wintera@linux.ibm.com, kgraul@linux.ibm.com,
	wenjia@linux.ibm.com, jaka@linux.ibm.com, hca@linux.ibm.com,
	twinkler@linux.ibm.com, raspl@linux.ibm.com,
	Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [virtio-dev] [PATCH v2 1/1] virtio-ism: introduce new device virtio-ism
Date: Thu, 12 Jan 2023 13:15:55 +0100	[thread overview]
Message-ID: <20230112131555.70836a62.pasic@linux.ibm.com> (raw)
In-Reply-To: <20230112014722-mutt-send-email-mst@kernel.org>

On Thu, 12 Jan 2023 01:56:14 -0500
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> I think fundamentally from spec POV memory is shared between devices.

Right, but with the gid stuff and the corresponding rules shared between
two or more arbitrary virtio-ism devices won't do. We need to find a way
to express the what device can communicate with what device relationship.

> How sharing is accomplished guest does not care so neither should the
> spec.

One of the goals of the spec is to foster interoperability. I wonder
how far that goes. For example one could imagine a shared memory on
the same host implementation by one vendor, and an RDMA based
implementation of an other vendor both implementing the very same
interface on the driver-device level. Two entities would not be
able to talk to each other via virtio-ism devices that use different
ways to accomplish the sharing. Is that out of scope for this spec?

> Can some RDMA tricks be used for synchronisation behind the
> scenes? 

I'm not familiar enough with RDMA. But I guess it may also depend on
the "memory consistency" and coherency properties. Which are not
specified for now for the ISM shared memory regions AFAIU.

> Maybe, the spec does not care. But we can give an example.
> 

At this point I'm not sure, whether the spec should care or not.

> So something like:
> 
> 	An ISM(Internal Shared Memory) device provides the ability to
> 	access memory shared between multiple devices. This allows low-overhead
> 	communication in presence of such memory. For example, memory can be
> 	shared with guests of multiple virtual machines running on the same
> 	host, with each virtual machine including an ISM device and with
> 	the guests using the ISM devices to access the shared memory.
> 
> what do others think?

I agree, the spec should be as abstract as possible. As stated above,
I don't have clarity on the interoperability goals. Is multiple flavors
of virtio-ism devices that are not mutually interoperable a good outcome?

Regards,
Halil


  parent reply	other threads:[~2023-01-12 12:15 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23  8:13 [PATCH v2 0/1] introduce virtio-ism: internal shared memory device Xuan Zhuo
2022-12-23  8:13 ` [PATCH v2 1/1] virtio-ism: introduce new device virtio-ism Xuan Zhuo
2023-01-10 22:34   ` [virtio-dev] " Halil Pasic
2023-01-11 11:08     ` Xuan Zhuo
2023-01-11 15:11       ` Halil Pasic
2023-01-12  2:01         ` Jason Wang
2023-01-12  6:56           ` Michael S. Tsirkin
2023-01-12  8:42             ` Cornelia Huck
2023-01-12 11:48               ` Xuan Zhuo
2023-01-12 14:30                 ` Cornelia Huck
2023-01-12 15:41                   ` Halil Pasic
2023-01-12 16:07                     ` Cornelia Huck
2023-01-13  1:58                     ` Xuan Zhuo
2023-01-13  2:29                       ` Jason Wang
2023-01-13  6:24                         ` Xuan Zhuo
2023-01-13 12:00                           ` Michael S. Tsirkin
2023-01-16  2:10                             ` Xuan Zhuo
2023-01-19 12:30                               ` Alexandra Winter
2023-01-28  7:42                                 ` Xuan Zhuo
2023-01-12 11:47             ` Xuan Zhuo
2023-01-12 12:15             ` Halil Pasic [this message]
2023-01-11 15:22       ` Halil Pasic
2023-01-12 11:57         ` Xuan Zhuo
2023-01-11 15:30       ` Halil Pasic
2023-01-12 12:03         ` Xuan Zhuo
2023-01-11 20:46       ` Halil Pasic
2023-01-12 12:23         ` Xuan Zhuo
2023-01-11 21:12       ` Halil Pasic
2023-01-12  7:01         ` Michael S. Tsirkin
2023-01-12 12:31         ` Xuan Zhuo
2023-01-20 13:06           ` Halil Pasic
2023-01-12 12:40         ` Xuan Zhuo
2023-02-05 12:30         ` Michael S. Tsirkin
2023-02-06  2:15           ` Xuan Zhuo
2023-01-25 12:55 ` [PATCH v2 0/1] introduce virtio-ism: internal shared memory device Wenjia Zhang
2023-03-01  9:34   ` Tony Lu
2023-03-01  9:34     ` [virtio-dev] " Tony Lu

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=20230112131555.70836a62.pasic@linux.ibm.com \
    --to=pasic@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=dust.li@linux.alibaba.com \
    --cc=gerry@linux.alibaba.com \
    --cc=hans@linux.alibaba.com \
    --cc=hca@linux.ibm.com \
    --cc=helinguo@linux.alibaba.com \
    --cc=herongguang@linux.alibaba.com \
    --cc=jaka@linux.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jasowang@redhat.com \
    --cc=kgraul@linux.ibm.com \
    --cc=mst@redhat.com \
    --cc=raspl@linux.ibm.com \
    --cc=tonylu@linux.alibaba.com \
    --cc=twinkler@linux.ibm.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=wenjia@linux.ibm.com \
    --cc=wintera@linux.ibm.com \
    --cc=xuanzhuo@linux.alibaba.com \
    --cc=zhenzao@linux.alibaba.com \
    --cc=zmlcc@linux.alibaba.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