From: Parav Pandit <parav@nvidia.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>,
"mst@redhat.com" <mst@redhat.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"pasic@linux.ibm.com" <pasic@linux.ibm.com>,
"cohuck@redhat.com" <cohuck@redhat.com>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>, Jiri Pirko <jiri@nvidia.com>
Subject: [virtio-dev] RE: [virtio-comment] [PATCH v4 2/8] transport-pci: Refer to the vq by its number
Date: Mon, 27 Mar 2023 23:19:35 +0000 [thread overview]
Message-ID: <PH0PR12MB54810F25B0E3069E18C8D9A4DC8B9@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <68fc71b0-2026-fd99-22f3-d0313e597373@nvidia.com>
> From: Max Gurtovoy <mgurtovoy@nvidia.com>
> Sent: Monday, March 27, 2023 6:49 PM
>
> > diff --git a/content.tex b/content.tex index 1ab7794..0f634ac 100644
> > --- a/content.tex
> > +++ b/content.tex
> > @@ -321,7 +321,7 @@ \section{Virtqueues}\label{sec:Basic Facilities of a
> Virtio Device / Virtqueues}
> > VIRTIO_F_IN_ORDER feature. If negotiated, this knowledge
> > might allow optimizations or simplify driver and/or device code.
> >
> > -Each virtqueue is identified as vq number or also referred
> > +Each virtqueue is identified by a vq number or also referred
> > to as a virtqueue number; vq number range is from 0 to 65535.
> >
>
> Please squash this to patch 1/8 were you introduced this line.
>
Latest v7 doesnt have this wrong hunk here.
>
>
> > Each virtqueue can consist of up to 3 parts:
> > diff --git a/transport-pci.tex b/transport-pci.tex index
> > b07a822..044c085 100644
> > --- a/transport-pci.tex
> > +++ b/transport-pci.tex
> > @@ -390,13 +390,15 @@ \subsubsection{Common configuration structure
> > layout}\label{sec:Virtio Transport
> >
> > \item[\field{queue_notify_data}]
> > This field exists only if VIRTIO_F_NOTIF_CONFIG_DATA has been
> negotiated.
> > - The driver will use this value to put it in the 'virtqueue number' field
> > - in the available buffer notification structure.
> > + The driver will use this value to put it in the field
> > + \field{vqn} in the available buffer notification
> > + structure.
>
> why do you add new lines here and bellow ?
>
Will fix in v8.
Below line addition is due to existing limit of 64 or 65 chars per line.
> > See section \ref{sec:Virtio Transport Options / Virtio Over PCI Bus / PCI-
> specific Initialization And Device Operation / Available Buffer Notifications}.
> > \begin{note}
> > This field provides the device with flexibility to determine how
> virtqueues
> > will be referred to in available buffer notifications.
> > - In a trivial case the device can set \field{queue_notify_data}=vqn. Some
> devices
> > + In a trivial case the device can set
> > + \field{queue_notify_data}=vq number. Some devices
> > may benefit from providing another value, for example an internal
> virtqueue
> > identifier, or an internal offset related to the virtqueue number.
> > \end{note}
> > @@ -1005,7 +1007,7 @@ \subsubsection{Device
> Initialization}\label{sec:Virtio Transport Options / Virti
> > The driver typically does this as follows, for each virtqueue a device has:
> >
> > \begin{enumerate}
> > -\item Write the virtqueue index (first queue is 0) to \field{queue_select}.
> > +\item Write the virtqueue number (first queue is 0) to \field{queue_select}.
> >
I noticed mentioning of first queue here which is not related.
Similar cleanup that Stefano suggested.
Fixing this in v8 too.
> > \item Read the virtqueue size from \field{queue_size}. This controls how big
> the virtqueue is
> > (see \ref{sec:Basic Facilities of a Virtio Device /
> Virtqueues}~\nameref{sec:Basic Facilities of a Virtio Device / Virtqueues}). If
> this field is 0, the virtqueue does not exist.
> > @@ -1035,7 +1037,7 @@ \subsubsection{Available Buffer
> > Notifications}\label{sec:Virtio Transport Option
> >
> > When VIRTIO_F_NOTIFICATION_DATA has not been negotiated,
> > the driver sends an available buffer notification to the device by
> > writing -the 16-bit virtqueue index
> > +the 16-bit virtqueue number
> > of this virtqueue to the Queue Notify address.
> >
> > When VIRTIO_F_NOTIFICATION_DATA has been negotiated, @@ -1053,7
> > +1055,7 @@ \subsubsection{Available Buffer Notifications}\label{sec:Virtio
> Transport Option
> > If VIRTIO_F_NOTIF_CONFIG_DATA has been negotiated:
> > \begin{itemize}
> > \item If VIRTIO_F_NOTIFICATION_DATA has not been negotiated, the
> > driver MUST use the -\field{queue_notify_data} value instead of the
> virtqueue index.
> > +\field{queue_notify_data} value instead of the virtqueue number.
> > \item If VIRTIO_F_NOTIFICATION_DATA has been negotiated, the driver
> MUST set the
> > \field{vqn} field to the \field{queue_notify_data} value.
> > \end{itemize}
>
> In general, after fixing the above minor comments - looks good.
>
> Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
Thanks. Will add your RB in v8 for this patch.
next prev parent reply other threads:[~2023-03-27 23:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 21:52 [virtio-dev] [PATCH v4 0/8] Rename queue index to queue number Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 1/8] content: Add vq number text Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 2/8] transport-pci: Refer to the vq by its number Parav Pandit
[not found] ` <68fc71b0-2026-fd99-22f3-d0313e597373@nvidia.com>
2023-03-27 23:19 ` Parav Pandit [this message]
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 3/8] transport-mmio: Rename QueueNum register Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 4/8] transport-mmio: Refer to the vq by its number Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 5/8] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 6/8] transport-ccw: Refer to the vq by its number Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 7/8] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-03-22 21:52 ` [virtio-dev] [PATCH v4 8/8] virtio-net: Describe RSS using receive queue handle Parav Pandit
2023-03-22 23:03 ` [virtio-dev] " Michael S. Tsirkin
2023-03-22 23:47 ` [virtio-dev] " Parav Pandit
2023-03-22 23:04 ` [virtio-dev] Re: [PATCH v4 0/8] Rename queue index to queue number Michael S. Tsirkin
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=PH0PR12MB54810F25B0E3069E18C8D9A4DC8B9@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=jiri@nvidia.com \
--cc=mgurtovoy@nvidia.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).