virtio-comment.lists.oasis-open.org archive mirror
 help / color / mirror / Atom feed
From: Alexandra Winter <wintera@linux.ibm.com>
To: Wen Gu <guwen@linux.alibaba.com>,
	Halil Pasic <pasic@linux.ibm.com>,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: virtio-comment@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, mst@redhat.com, cohuck@redhat.com,
	jasowang@redhat.com, Jan Kiszka <jan.kiszka@siemens.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,
	virtio-dev@lists.oasis-open.org
Subject: [virtio-comment] Re: [virtio-dev] Re: [virtio-comment] [PATCH v3 1/1] virtio-ism: introduce new device virtio-ism
Date: Wed, 5 Apr 2023 14:39:53 +0200	[thread overview]
Message-ID: <7a9ebec0-5e87-b80f-4f2c-c4db7ae4fe84@linux.ibm.com> (raw)
In-Reply-To: <ff9b28a1-e0ee-f082-1f40-f3e149c9403e@linux.alibaba.com>



On 24.03.23 05:03, Wen Gu wrote:
> 
> 
> On 2023/3/23 22:46, Halil Pasic wrote:
> 
>> On Thu,  9 Feb 2023 11:30:56 +0800
>> Xuan Zhuo <xuanzhuo@linux.alibaba.com> wrote:
>>

...

> 
>> To get back to the things proposed here: the cdid is IMHO
>> a nice thing, and is functionally corresponding to the
>> (S)EID. But it is 16 byte wide, and I have no idea how
>> is it supposed to be used in the CLC handshake.
>>
> 
> CLC handshake carry one SEID for all the SMC-D device. Considering
> coexistence with ISM, I am not sure whether we can change or increase
> the SEID.. cc Alexandra
> 
> Thanks!
> Wen Gu

As mentioned by others, discussions are ongoing.
It would be great, if we can agree on a way to use the existing CLC handshake
for SMC-D via virtio-ism and ism-loopback.
In that case SEID needs to be unique per hardware instance, cannot be increased and
can only be changed for x86 in a non-colliding way.

An alternative would be to define new a SMC-D(?) protocol variant/version, where we
are free to define new fields (e.g. UUIDs).

Alexandra

> 
>> If this is really supposed to work with SMC and not just take
>> inspiration from it, I would like some insight from our
>> SMC experts (they are already on copy).
>>
>> Regards,
>> Halil
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org

This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  parent reply	other threads:[~2023-04-05 12:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  3:30 [PATCH v3 0/1] introduce virtio-ism: internal shared memory device Xuan Zhuo
2023-02-09  3:30 ` [PATCH v3 1/1] virtio-ism: introduce new device virtio-ism Xuan Zhuo
2023-02-09  3:35   ` [virtio-comment] " Parav Pandit
2023-02-09  3:36     ` Xuan Zhuo
2023-03-07 11:15   ` [virtio-comment] " Xuan Zhuo
2023-03-15 11:15     ` Xuan Zhuo
2023-03-23 14:46   ` [virtio-comment] " Halil Pasic
2023-03-24  3:08     ` Xuan Zhuo
     [not found]     ` <ff9b28a1-e0ee-f082-1f40-f3e149c9403e@linux.alibaba.com>
2023-04-05 12:39       ` Alexandra Winter [this message]
2023-04-05 12:52         ` [virtio-comment] Re: [virtio-dev] " Michael S. Tsirkin
2023-04-05 13:02           ` Alexandra Winter
2023-04-05 13:06             ` Fwd: " Alexandra Winter
2023-04-07  3:25               ` Xuan Zhuo
2023-04-07 11:16                 ` Michael S. Tsirkin
2023-04-07  3:22           ` Xuan Zhuo
2023-04-07 11:13             ` Michael S. Tsirkin
2023-04-10  1:47               ` Xuan Zhuo
2023-04-10  1:23             ` Jason Wang
2023-04-10  1:53               ` Xuan Zhuo
2023-04-10  2:04                 ` Jason Wang
2023-03-24  4:51   ` Parav Pandit
2023-03-24  6:35     ` Xuan Zhuo
2023-03-24  9:10     ` Michael S. Tsirkin
2023-04-26  7:41   ` [virtio-comment] " Xuan Zhuo

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=7a9ebec0-5e87-b80f-4f2c-c4db7ae4fe84@linux.ibm.com \
    --to=wintera@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=dust.li@linux.alibaba.com \
    --cc=gerry@linux.alibaba.com \
    --cc=guwen@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=pasic@linux.ibm.com \
    --cc=raspl@linux.ibm.com \
    --cc=tonylu@linux.alibaba.com \
    --cc=twinkler@linux.ibm.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=wenjia@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;
as well as URLs for NNTP newsgroup(s).