From: "Michael S. Tsirkin" <mst@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Cornelia Huck" <cohuck@redhat.com>,
"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>,
virtio-comment@lists.linux.dev
Subject: Re: [PATCH V7] virtio-transport: Add a new section to clarify transport requirements
Date: Thu, 25 Jul 2024 05:28:05 -0400 [thread overview]
Message-ID: <20240725052410-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240725091544.kmiij443daqnzkja@vireshk-i7>
On Thu, Jul 25, 2024 at 02:45:44PM +0530, Viresh Kumar wrote:
> On 24-07-24, 07:05, Michael S. Tsirkin wrote:
> > I don't know do you keep talking about "pair" everywhere.
>
> This came from one of the review comments and so I tried to use the same
> language everywhere.
>
> > Just say "the device and the driver" or "a device and a driver" as
> > apporpriate. And in many cases it is actually just one of these.
>
> That's a mistake then. Will fix it.
>
> > > +This section specifies the mandatory requirements that any transport
> > > +needs to implement.
> > > +
> > > +\section{Transport Requirements}\label{sec:Creating New Transports / Transport Requirements}
> > > +
> > > +A transport provides a mechanism to implement configuration space
> > > +between a pair of device-driver.
> >
> > configuration space is not "between".
>
> "... implement configuration space for the device and the driver."
just the device
> > > +A transport provides a mechanism for a pair of device-driver to
> > > +communicate virtqueue configurations and virtqueue memory location.
> >
> > this is only communicated one way
>
> "A transport provides a mechanism for the device to communicate virtqueue
> configurations and memory location to the driver."
not really, it's normally the driver that communicates all this.
and configuration is it's own plural I think.
> > > +A transport provides a mechanism for the driver to identify the device
> > > +type.
> > > +
> > > +A transport allows one or more virtqueues for a given device-driver
> > > +pair.
> >
> > no idea what does virtqueues for a pair mean.
>
> "A transport allows one or more virtqueues to be implemented for a device and a
> driver."
by the device
> > > The number of virtqueues per pair are governed by the individual
> > > +device protocol.
> >
> > what is device protocol?
>
> "The number of virtqueues are governed by the device implementation."
what are you trying to say? that transport does not need to
specify this?
basically we can just kill this sentence then?
> > > +A transport provides a mechanism for the device and driver to notify
> > > +each other, for example regarding availability of a buffer on the
> > > +virtqueue.
> >
> > notify should be more specific. about vq events?
> > this is only notified one way, not "each other".
>
> "A transport provides a mechanism for the device to send a virtqueue event to
> the driver, for example regarding availability of a buffer on the virtqueue."
/facepalm
this just messes up terminology completely.
pls check what we say about device and driver notifications and follow
that terminology
> > > +A transport provides a mechanism for the driver to initiate a reset of
> > > +the device.
> > > +
> > > +A transport provides a mechanism for the driver to read or modify the
> > > +device status.
> >
> > I don't think reading status is strictly required, except for
> > FEATURES_OK bit.
>
> "A transport provides a mechanism for the driver to read the FEATURES_OK bit."
status bit
>
> "A transport provides a mechanism for the driver to modify the device status."
>
> --
> viresh
next prev parent reply other threads:[~2024-07-25 9:28 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
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 [this message]
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=20240725052410-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--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