From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: virtio-comment@lists.linux.dev,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Parav Pandit" <parav@nvidia.com>,
"Matias Ezequiel Vara Larsen" <mvaralar@redhat.com>
Subject: Re: [PATCH V7] virtio-transport: Add a new section to clarify transport requirements
Date: Thu, 11 Jul 2024 13:46:19 +0200 [thread overview]
Message-ID: <87zfqob184.fsf@redhat.com> (raw)
In-Reply-To: <20240711070740-mutt-send-email-mst@kernel.org>
On Thu, Jul 11 2024, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Thu, Jul 11, 2024 at 01:18:18PM +0530, Viresh Kumar wrote:
>> The virtio documentation currently doesn't define any generic
>> requirements that are applicable to all transports. They can be useful
>> while adding support for a new transport.
>>
>> This commit tries to define the same under a new Appendix section.
>>
>> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
>> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>> ---
>
> I am not sure what is this supposed doing - just listing basic things
> transport does or all things it can do?
>
> If the later, this ignores several things that transports can do,
> such as shared memory, data in notification, etc.
Maybe split this up?
A transport needs to implement the following:
<list of mandatory things>
A transport is encouraged to implement the following:
<list of non-mandatory, but strongly suggested things>
next prev parent reply other threads:[~2024-07-11 11:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 7:48 [PATCH V7] virtio-transport: Add a new section to clarify transport requirements Viresh Kumar
2024-07-11 8:24 ` Cornelia Huck
2024-07-11 9:05 ` Viresh Kumar
2024-07-11 10:59 ` Michael S. Tsirkin
2024-07-11 8:41 ` Stefano Garzarella
2024-07-11 9:23 ` Viresh Kumar
2024-07-11 11:07 ` Michael S. Tsirkin
2024-07-11 11:10 ` Michael S. Tsirkin
2024-07-11 11:46 ` Cornelia Huck [this message]
2024-07-11 11:51 ` Michael S. Tsirkin
2024-07-11 11:59 ` Cornelia Huck
2024-07-11 14:30 ` Michael S. Tsirkin
2024-07-11 14:44 ` Cornelia Huck
2024-07-11 14:49 ` Michael S. Tsirkin
2024-07-11 14:59 ` Cornelia Huck
2024-07-24 10:45 ` Viresh Kumar
2024-07-24 11:05 ` Michael S. Tsirkin
2024-07-25 9:15 ` Viresh Kumar
2024-07-25 9:28 ` Michael S. Tsirkin
2024-07-25 10:55 ` Viresh Kumar
2024-07-25 12:24 ` Michael S. Tsirkin
2024-07-29 3:36 ` Viresh Kumar
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=87zfqob184.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=manos.pitsidianakis@linaro.org \
--cc=mst@redhat.com \
--cc=mvaralar@redhat.com \
--cc=parav@nvidia.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=virtio-comment@lists.linux.dev \
/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