From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>
Subject: [virtio-comment] Re: [virtio] [PATCH] virtio-net: clarify error handling for coalescing
Date: Fri, 26 Jan 2024 03:01:11 -0500 [thread overview]
Message-ID: <20240126025730-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481FF7AED1F50D7066AC16ADC7B2@PH0PR12MB5481.namprd12.prod.outlook.com>
On Wed, Jan 24, 2024 at 11:23:08AM +0000, Parav Pandit wrote:
>
>
> > From: virtio@lists.oasis-open.org <virtio@lists.oasis-open.org> On Behalf Of
> > Michael S. Tsirkin
> > Sent: Wednesday, January 24, 2024 4:46 PM
> > To: virtio-comment@lists.oasis-open.org; virtio-dev@lists.oasis-open.org
> > Cc: virtio@lists.oasis-open.org
>
> Can we please avoid posting to three different lists?
Yea I'll stop. Used to do it because of different archiving rules.
I'll stick to virtio-comment@lists.oasis-open.org
> > Subject: [virtio] [PATCH] virtio-net: clarify error handling for coalescing
> >
> > This is not a huge deal since it's a SHOULD anyway, so make the new
> > requirement SHOULD too.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > device-types/net/description.tex | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/device-types/net/description.tex b/device-
> > types/net/description.tex
> > index aff5e08..d1d25fe 100644
> > --- a/device-types/net/description.tex
> > +++ b/device-types/net/description.tex
> > @@ -1792,7 +1792,11 @@ \subsubsection{Control
> > Virtqueue}\label{sec:Device Types / Network Device / Devi
> >
> > The device MUST ignore \field{reserved}.
> >
> > -The device SHOULD respond to VIRTIO_NET_CTRL_NOTF_COAL_TX_SET and
> > VIRTIO_NET_CTRL_NOTF_COAL_RX_SET commands with VIRTIO_NET_ERR if
> > it was not able to change the parameters.
> > +The device SHOULD respond to VIRTIO_NET_CTRL_NOTF_COAL_TX_SET and
> > +VIRTIO_NET_CTRL_NOTF_COAL_RX_SET commands with VIRTIO_NET_ERR
> > if it was
> > +not able to change coalescing parameters. In this case, the parameters
> > +SHOULD remain unchanged, for all VQs.
>
> Is the new added normative line without device is ok?
>
> Or should it be written as
> ... In this case, the device SHOULD not update the parameters for all VQs.
>
> ?
Your wording is confusing it can be intepreted to
mean just that not all parameters change but some might.
Generally we do not have to repeat "device" in each sentence.
> > +
> >
> > The device MUST respond to the VIRTIO_NET_CTRL_NOTF_COAL_VQ_SET
> > command with VIRTIO_NET_ERR if it was not able to change the parameters.
> >
> > --
> > MST
> For the functionality itself, ignoring above normative suggestion,
>
> Reviewed-by: Parav Pandit <parav@nvidia.com>
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/
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>
Subject: [virtio-dev] Re: [virtio] [PATCH] virtio-net: clarify error handling for coalescing
Date: Fri, 26 Jan 2024 03:01:11 -0500 [thread overview]
Message-ID: <20240126025730-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481FF7AED1F50D7066AC16ADC7B2@PH0PR12MB5481.namprd12.prod.outlook.com>
On Wed, Jan 24, 2024 at 11:23:08AM +0000, Parav Pandit wrote:
>
>
> > From: virtio@lists.oasis-open.org <virtio@lists.oasis-open.org> On Behalf Of
> > Michael S. Tsirkin
> > Sent: Wednesday, January 24, 2024 4:46 PM
> > To: virtio-comment@lists.oasis-open.org; virtio-dev@lists.oasis-open.org
> > Cc: virtio@lists.oasis-open.org
>
> Can we please avoid posting to three different lists?
Yea I'll stop. Used to do it because of different archiving rules.
I'll stick to virtio-comment@lists.oasis-open.org
> > Subject: [virtio] [PATCH] virtio-net: clarify error handling for coalescing
> >
> > This is not a huge deal since it's a SHOULD anyway, so make the new
> > requirement SHOULD too.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > device-types/net/description.tex | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/device-types/net/description.tex b/device-
> > types/net/description.tex
> > index aff5e08..d1d25fe 100644
> > --- a/device-types/net/description.tex
> > +++ b/device-types/net/description.tex
> > @@ -1792,7 +1792,11 @@ \subsubsection{Control
> > Virtqueue}\label{sec:Device Types / Network Device / Devi
> >
> > The device MUST ignore \field{reserved}.
> >
> > -The device SHOULD respond to VIRTIO_NET_CTRL_NOTF_COAL_TX_SET and
> > VIRTIO_NET_CTRL_NOTF_COAL_RX_SET commands with VIRTIO_NET_ERR if
> > it was not able to change the parameters.
> > +The device SHOULD respond to VIRTIO_NET_CTRL_NOTF_COAL_TX_SET and
> > +VIRTIO_NET_CTRL_NOTF_COAL_RX_SET commands with VIRTIO_NET_ERR
> > if it was
> > +not able to change coalescing parameters. In this case, the parameters
> > +SHOULD remain unchanged, for all VQs.
>
> Is the new added normative line without device is ok?
>
> Or should it be written as
> ... In this case, the device SHOULD not update the parameters for all VQs.
>
> ?
Your wording is confusing it can be intepreted to
mean just that not all parameters change but some might.
Generally we do not have to repeat "device" in each sentence.
> > +
> >
> > The device MUST respond to the VIRTIO_NET_CTRL_NOTF_COAL_VQ_SET
> > command with VIRTIO_NET_ERR if it was not able to change the parameters.
> >
> > --
> > MST
> For the functionality itself, ignoring above normative suggestion,
>
> Reviewed-by: Parav Pandit <parav@nvidia.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2024-01-26 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 11:15 [virtio-comment] [PATCH] virtio-net: clarify error handling for coalescing Michael S. Tsirkin
2024-01-24 11:15 ` [virtio-dev] " Michael S. Tsirkin
2024-01-24 11:23 ` [virtio-comment] RE: [virtio] " Parav Pandit
2024-01-24 11:23 ` [virtio-dev] " Parav Pandit
2024-01-26 8:01 ` Michael S. Tsirkin [this message]
2024-01-26 8:01 ` [virtio-dev] " Michael S. Tsirkin
2024-01-24 11:28 ` [virtio-comment] " Heng Qi
2024-01-24 11:28 ` [virtio-dev] " Heng Qi
2024-01-29 15:06 ` [virtio-comment] Re: [virtio] " Cornelia Huck
2024-01-29 15:06 ` [virtio-dev] " Cornelia Huck
2024-01-29 16:26 ` [virtio-comment] " Michael S. Tsirkin
2024-01-29 16:26 ` [virtio-dev] " Michael S. Tsirkin
2024-01-29 16:55 ` [virtio-comment] " Cornelia Huck
2024-01-29 16:55 ` [virtio-dev] " 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=20240126025730-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@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 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.