From: Hao Chen <chenhaosjtuacm@google.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] [PATCH] Add virtio parameter server device specification
Date: Wed, 2 Jun 2021 13:09:39 -0700 [thread overview]
Message-ID: <CABATKF-t-xfj0cTa6zsnKJwLbXUCLaSZOqUWXDEOfKpR3KCPgw@mail.gmail.com> (raw)
In-Reply-To: <40119ebe-04c5-ce46-e015-6e69086f2186@metux.net>
> If your goal is just to have a standard protocol then I think you can make
> it much easier for others to implement by publishing your own protocol
> spec that runs over a vsock socket.
> If its just reading / setting some kind of "variables" via some path
> name, why not using 9P for that ?
We can use any protocol to implement this, and publish it somewhere, but it
does not carry the same weight as putting it in the virtio spec. It is
easier to say
"we use virtio, and for this device we use virtio-xxx device", but it
would be weird to
say "we use virtio, but for this device, we use vsock+some other non-standard
protocol, please support this or you will break the compatibility".
That is why we
want to put parameter server as a new virtio device.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2021-06-02 20:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 0:33 [virtio-dev] [PATCH] Add virtio parameter server device specification Hao Chen
2021-04-30 10:55 ` Cornelia Huck
2021-05-07 23:06 ` Hao Chen
2021-05-11 9:24 ` Cornelia Huck
2021-05-13 14:46 ` Stefan Hajnoczi
2021-05-17 19:28 ` Hao Chen
[not found] ` <20210517193030.1568902-1-chenhaosjtuacm@google.com>
2021-05-17 19:32 ` [virtio-dev] [PATCH v2] " Hao Chen
[not found] ` <20210517193617.1576401-1-chenhaosjtuacm@google.com>
2021-05-17 19:37 ` [virtio-dev] Fwd: [PATCH v3] " Hao Chen
2021-05-19 17:01 ` [virtio-dev] " Cornelia Huck
2021-05-18 6:02 ` [virtio-dev] [PATCH] " Enrico Weigelt, metux IT consult
2021-05-18 21:56 ` Hao Chen
2021-06-02 13:48 ` Enrico Weigelt, metux IT consult
2021-06-02 20:09 ` Hao Chen [this message]
2021-06-04 10:50 ` Enrico Weigelt, metux IT consult
2021-06-09 20:30 ` Hao Chen
2021-06-10 16:06 ` Enrico Weigelt, metux IT consult
2021-06-10 23:15 ` Hao Chen
[not found] ` <20210610231954.2937837-1-chenhaosjtuacm@google.com>
2021-06-10 23:20 ` [virtio-dev] Re: [PATCH v4] " Hao Chen
2021-06-11 18:44 ` Hao Chen
2021-09-08 20:42 ` Hao Chen
[not found] ` <CABATKF9kqVOeR44vcTH_aw5Sx9geT0-gVpyqngcAwnkcxVN35Q@mail.gmail.com>
2021-10-04 18:30 ` Hao Chen
2021-05-24 14:37 ` [virtio-dev] [PATCH] " Stefan Hajnoczi
2021-05-24 18:45 ` Hao Chen
2021-05-25 16:56 ` Stefan Hajnoczi
2021-06-09 9:12 ` Stefan Hajnoczi
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=CABATKF-t-xfj0cTa6zsnKJwLbXUCLaSZOqUWXDEOfKpR3KCPgw@mail.gmail.com \
--to=chenhaosjtuacm@google.com \
--cc=lkml@metux.net \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.oasis-open.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 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.