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 08:24:08 -0400 [thread overview]
Message-ID: <20240725081757-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240725105524.sucisnw2djjzewed@vireshk-i7>
On Thu, Jul 25, 2024 at 04:25:24PM +0530, Viresh Kumar wrote:
> On 25-07-24, 05:28, Michael S. Tsirkin wrote:
> > On Thu, Jul 25, 2024 at 02:45:44PM +0530, Viresh Kumar wrote:
> > > "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.
>
> Ah.
>
> > and configuration is it's own plural I think.
>
> Hmm, Wikipedia [1] and chatgpt say otherwise.
>
> Anyway, "configuration" is fine here.
The configuration as used here is its own plural.
Here's an explanation if you want the detail - not
because a random website is an expert but just because it
happens to be right.
https://www.wordhippo.com/what-is/the-plural-of/configuration.html
> > > > > 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?
>
> Hmm, from what I understand the individual device implementation (protocol as
> specified in the virtio-specification, for example I2C, SPI, etc.) specify the
> exact number of virtqueues that are required for their working. I am not sure
> how a transport changes that.
No it's an i2c device, not i2c protocol. The i2c, spi etc protocols are
outside of virtio spec and have nothing to do with virtqueues.
>
> Please suggest how you think this must be written then.
I still don't know what you want to say.
Virtio spec just calls them "specific devices".
Are you trying to say:
The number of virtqueues is device specific and not specified by the
transport.
> > pls check what we say about device and driver notifications and follow
> > that terminology
>
> "A transport provides a mechanism for the device to send the configuration
> change notifications and used buffer notifications to the driver."
>
> "A transport provides a mechanism for the driver to send the available buffer
> notifications to the device."
you can just say "device notifications" and "driver notifications",
respectively, there might be more down the road.
>
> --
> viresh
>
> [1] https://en.wiktionary.org/wiki/configuration
next prev parent reply other threads:[~2024-07-25 12:24 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
2024-07-25 10:55 ` Viresh Kumar
2024-07-25 12:24 ` Michael S. Tsirkin [this message]
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=20240725081757-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 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.