From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Vitaly Mireyno <vmireyno@marvell.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [virtio-comment] [PATCH] virtio-net: Add an optional device control over the receive buffers length
Date: Sun, 5 Jan 2020 05:28:27 -0500 [thread overview]
Message-ID: <20200105052521-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200103152244.GF277936@stefanha-x1.localdomain>
On Fri, Jan 03, 2020 at 03:22:44PM +0000, Stefan Hajnoczi wrote:
> On Mon, Dec 30, 2019 at 01:59:17PM +0000, Vitaly Mireyno wrote:
> > @@ -2916,6 +2933,15 @@ \subsection{Device configuration layout}\label{sec:Device Types / Network Device
> > If the driver negotiates the VIRTIO_NET_F_STANDBY feature, the device MAY act
> > as a standby device for a primary device with the same MAC address.
> >
> > +A driver SHOULD accept the VIRTIO_NET_F_RXBUF_MIN_LEN feature if offered.
> > +
> > +If VIRTIO_NET_F_RXBUF_MIN_LEN feature has been negotiated, the driver MUST
> > +set \field{min_rx_buf_len}.
> > +
> > +A driver MUST NOT modify \field{min_rx_buf_len} once it has been set.
>
> When must the driver set the fields? I guess it makes no sense to set
> this field after starting rx (i.e. populating the rx virtqueue)... The
> spec should be explicit about this.
If we are going to keep it static then I think the best time is
before features ok.
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:[~2020-01-05 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 13:59 [virtio-comment] [PATCH] virtio-net: Add an optional device control over the receive buffers length Vitaly Mireyno
2020-01-03 15:22 ` Stefan Hajnoczi
2020-01-05 10:28 ` Michael S. Tsirkin [this message]
2020-01-05 10:35 ` [virtio-comment] " Michael S. Tsirkin
2020-01-20 16:24 ` [virtio-comment] " Michael S. Tsirkin
2020-01-22 16:06 ` [virtio-comment] RE: [EXT] " Vitaly Mireyno
2020-01-23 6:55 ` [virtio-comment] " Michael S. Tsirkin
2020-01-23 7:10 ` Jason Wang
2020-01-23 7:46 ` Michael S. Tsirkin
2020-01-23 10:00 ` Jason Wang
2020-01-23 12:08 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2020-01-26 8:21 Vitaly Mireyno
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=20200105052521-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=vmireyno@marvell.com \
/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