From: David Edmondson <david.edmondson@oracle.com>
To: Parav Pandit <parav@nvidia.com>
Cc: mst@redhat.com, virtio-dev@lists.oasis-open.org,
cohuck@redhat.com, shahafs@nvidia.com,
virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH v3 2/2] virtio-net: Define cfg fields before description
Date: Mon, 20 Feb 2023 14:42:40 +0000 [thread overview]
Message-ID: <m2fsb0e6pk.fsf@oracle.com> (raw)
In-Reply-To: <20230217154529.33508-3-parav@nvidia.com>
On Friday, 2023-02-17 at 17:45:29 +02, Parav Pandit wrote:
> Currently some fields of the virtio_net_config structure are defined
> before introducing the structure and some are defined after
> introducing virtio_net_config.
> Better to define the configuration layout first followed by
> description of all the fields.
>
> Device configuration fields are described in the section. Change wording
> from 'listed' to 'described' as suggested in patch [1].
>
> [1] https://lists.oasis-open.org/archives/virtio-dev/202302/msg00004.html
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/161
> Signed-off-by: Parav Pandit <parav@nvidia.com>
Reviewed-by: David Edmondson <david.edmondson@oracle.com>
> ---
> changelog:
> v2->v3:
> - split the patch for read only description as prepration patch
> v1->v2:
> - remove read-only wording from multiple places
> v0->v1:
> - Change wording about device configuration field introduction
> - remove duplicate read-only wording for status field
> - reword sentence to read it better
> ---
> device-types/net/description.tex | 40 ++++++++++++++++++--------------
> 1 file changed, 22 insertions(+), 18 deletions(-)
>
> diff --git a/device-types/net/description.tex b/device-types/net/description.tex
> index 81e1135..c4bb64e 100644
> --- a/device-types/net/description.tex
> +++ b/device-types/net/description.tex
> @@ -156,11 +156,28 @@ \subsubsection{Legacy Interface: Feature bits}\label{sec:Device Types / Network
> \subsection{Device configuration layout}\label{sec:Device Types / Network Device / Device configuration layout}
> \label{sec:Device Types / Block Device / Feature bits / Device configuration layout}
>
> -Device configuration fields are listed below. The \field{mac} address field
> -always exists (though is only valid if VIRTIO_NET_F_MAC is set), and
> -\field{status} only exists if VIRTIO_NET_F_STATUS is set. Two
> -bits (for the driver) are currently defined for the status field:
> -VIRTIO_NET_S_LINK_UP and VIRTIO_NET_S_ANNOUNCE.
> +The network device has the following device configuration layout.
> +
> +\begin{lstlisting}
> +struct virtio_net_config {
> + u8 mac[6];
> + le16 status;
> + le16 max_virtqueue_pairs;
> + le16 mtu;
> + le32 speed;
> + u8 duplex;
> + u8 rss_max_key_size;
> + le16 rss_max_indirection_table_length;
> + le32 supported_hash_types;
> +};
> +\end{lstlisting}
> +
> +The \field{mac} address field always exists (although it is only
> +valid if VIRTIO_NET_F_MAC is set).
> +
> +The \field{status} only exists if VIRTIO_NET_F_STATUS is set.
> +Two bits are currently defined for the status field: VIRTIO_NET_S_LINK_UP
> +and VIRTIO_NET_S_ANNOUNCE.
>
> \begin{lstlisting}
> #define VIRTIO_NET_S_LINK_UP 1
> @@ -190,19 +207,6 @@ \subsection{Device configuration layout}\label{sec:Device Types / Network Device
> is expected to re-read these values after receiving a
> configuration change notification.
>
> -\begin{lstlisting}
> -struct virtio_net_config {
> - u8 mac[6];
> - le16 status;
> - le16 max_virtqueue_pairs;
> - le16 mtu;
> - le32 speed;
> - u8 duplex;
> - u8 rss_max_key_size;
> - le16 rss_max_indirection_table_length;
> - le32 supported_hash_types;
> -};
> -\end{lstlisting}
> The following field, \field{rss_max_key_size} only exists if VIRTIO_NET_F_RSS or VIRTIO_NET_F_HASH_REPORT is set.
> It specifies the maximum supported length of RSS key in bytes.
--
Tell me sweet little lies.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2023-02-20 14:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 15:45 [virtio-comment] [PATCH v3 0/2] virtio-net: Improve dev config layout Parav Pandit
2023-02-17 15:45 ` [PATCH v3 1/2] virtio-net: Describe dev cfg fields read only Parav Pandit
2023-02-20 14:46 ` [virtio-dev] " David Edmondson
2023-02-21 15:37 ` [virtio-dev] " Cornelia Huck
2023-02-21 17:42 ` Michael S. Tsirkin
2023-02-21 17:50 ` Parav Pandit
2023-02-21 17:52 ` Michael S. Tsirkin
2023-02-21 17:59 ` Parav Pandit
2023-02-21 18:08 ` Michael S. Tsirkin
2023-02-22 9:01 ` [virtio-dev] " Cornelia Huck
2023-02-22 11:50 ` Michael S. Tsirkin
2023-02-22 12:07 ` [virtio-comment] " Cornelia Huck
2023-02-22 12:55 ` Michael S. Tsirkin
2023-02-22 13:26 ` [virtio-comment] " Cornelia Huck
2023-02-23 5:50 ` Parav Pandit
2023-02-17 15:45 ` [PATCH v3 2/2] virtio-net: Define cfg fields before description Parav Pandit
2023-02-20 14:42 ` David Edmondson [this message]
2023-02-21 13:30 ` [PATCH v3 0/2] virtio-net: Improve dev config layout Parav Pandit
[not found] ` <875ybej6hb.fsf@redhat.com>
2023-03-07 17:25 ` [virtio-dev] " Parav Pandit
2023-03-08 10:07 ` [virtio-dev] Re: [virtio-comment] " Cornelia Huck
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=m2fsb0e6pk.fsf@oracle.com \
--to=david.edmondson@oracle.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.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