From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Vitaly Mireyno <vmireyno@marvell.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>
Subject: Re: [virtio-comment] Re: [EXT] Re: [virtio-comment] Re: [PATCH] virtio-net: Add equal-sized receive buffers feature
Date: Mon, 25 Nov 2019 03:30:26 -0500 [thread overview]
Message-ID: <20191125032811-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <d8ba4b97-5835-6a7e-f32a-d46ba5dfa9dd@redhat.com>
On Mon, Nov 25, 2019 at 04:22:47PM +0800, Jason Wang wrote:
>
> On 2019/11/25 下午4:18, Michael S. Tsirkin wrote:
> > > > > > Again I can see how we might want to disallow crazy setups with e.g. 1
> > > > > > byte per buffer. That's just abuse, no guest does that anyway. So asking
> > > > > > e.g. for a minimal buffer size sounds very reasonable.
> > > > > One question here is that, the minimal buffer size should depends on various
> > > > > factors. E.g the ring size. Consider a 256 entries ring, the minimal size
> > > > > should be 64K/256=256 ...
> > > > I guess you are right. We can make this driver programmable I guess?
> > > > Basically pass min_buf_len to the device.
> > > Then it still have the chance to program the min_buf_len to 1?
> > If it wants to - yes - presumably device won't work as well,
> > fetching all kind of extra data e.g. unnecessary descriptors.
> >
>
> Technically, device should still work for small packet and drop large
> packet.
I am not sure I agree. How is this different from just not being
sufficient space in the RX ring? We certainly do not want to
drop packets just because there's not enough buffers -
it's a temporary condition.
> Vhost has a bug that will stall RX in the case.
I think we want to spec this first then.
> Will post a fix.
>
> Thanks
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:[~2019-11-25 8:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 10:46 [virtio-comment] Re: [PATCH] virtio-net: Add equal-sized receive buffers feature Vitaly Mireyno
2019-11-01 4:09 ` Michael S. Tsirkin
2019-11-01 7:22 ` Jason Wang
2019-11-05 18:51 ` Michael S. Tsirkin
2019-11-10 14:13 ` [virtio-comment] RE: [EXT] " Vitaly Mireyno
2019-11-10 15:34 ` [virtio-comment] " Michael S. Tsirkin
2019-11-11 13:58 ` [virtio-comment] " Vitaly Mireyno
2019-11-11 15:05 ` [virtio-comment] " Michael S. Tsirkin
2019-11-14 15:49 ` [virtio-comment] " Vitaly Mireyno
2019-11-20 13:23 ` [virtio-comment] " Michael S. Tsirkin
2019-11-24 15:02 ` [virtio-comment] " Vitaly Mireyno
2019-11-24 15:30 ` [virtio-comment] " Michael S. Tsirkin
2019-11-25 3:31 ` Jason Wang
2019-11-25 7:33 ` Michael S. Tsirkin
2019-11-25 8:07 ` Jason Wang
2019-11-25 8:18 ` Michael S. Tsirkin
2019-11-25 8:22 ` Jason Wang
2019-11-25 8:30 ` Michael S. Tsirkin [this message]
2019-11-25 9:46 ` Jason Wang
2019-11-26 17:27 ` Vitaly Mireyno
2019-11-27 13:51 ` Michael S. Tsirkin
2019-12-01 10:22 ` Vitaly Mireyno
2019-12-01 13:07 ` Michael S. Tsirkin
2019-12-01 21:43 ` Michael S. Tsirkin
2019-12-02 15:09 ` Vitaly Mireyno
2019-12-02 15:23 ` Michael S. Tsirkin
2019-12-02 16:16 ` Vitaly Mireyno
2019-12-02 16:47 ` 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=20191125032811-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@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