From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Heng Qi <hengqi@linux.alibaba.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
David Edmondson <david.edmondson@oracle.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [virtio-dev] RE: RE: RE: RE: [PATCH v16] virtio-net: support device stats
Date: Mon, 4 Sep 2023 09:28:22 -0400 [thread overview]
Message-ID: <20230904092711-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54813CB40389462B1667184ADCE9A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Mon, Sep 04, 2023 at 12:21:48PM +0000, Parav Pandit wrote:
> > From: Heng Qi <hengqi@linux.alibaba.com>
> > Sent: Monday, September 4, 2023 4:41 PM
> >
> > 在 2023/9/4 下午6:26, Parav Pandit 写道:
> > >> From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > >> Sent: Monday, September 4, 2023 2:23 PM
> > >
> > >>> "The device MUST NOT pass received packets that exceed mtu (plus low
> > >>> level ethernet header length) size with gso_type NONE or ECN after
> > >> VIRTIO_NET_F_MTU has been successfully negotiated."
> > >>
> > >> NO.
> > >>
> > >> If the mtu is 1500, we can pass 64k packets to the driver with
> > >> gso_type (not NONE).
> > > Any supporting citation to spec for above comment?
> >
> > I think it can be referred here:
> > "The converse features are also available: a driver can save the virtual device
> > some work by negotiating these features. Note: For example, a network packet
> > transported between two guests on the same system might not need
> > checksumming at all, nor segmentation, if both guests are amenable."
> >
> Sure, it can avoid segmentation, but not at the cost of skipping mtu check.
> For example, sender sends skb with gso with each segment of 9K, and
> receiver has mtu of 1500, same skb without segmentation is not good.
> Because gso_size should be same as 1500 to match the mtu. One can say
> with violation of line " The device MUST NOT pass received packets..."
> things still work fine because guest is amenable. :)
>
> So counter looks ok to me when VIRTIO_NET_F_MTU is not negotiated or
> when mtu matches.
If someone misconfigures the LAN with different devices using
different MTU values .... all bets are off. OK we can put something
in spec e.g. for debugging but really just don't do this.
> > >
> > > Each packet must be 1500 for the mtu normative above.
> > > gso_size to <= mtu (ingoring the hdr math for simplicity for now).
> > > whole GSO completion can be for 64K to be reported in used_elem.len.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
> > > For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
>
---------------------------------------------------------------------
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:[~2023-09-04 13:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 5:52 [virtio-dev] [PATCH v16] virtio-net: support device stats Xuan Zhuo
2023-09-01 13:58 ` [virtio-dev] " Parav Pandit
2023-09-01 14:45 ` [virtio-dev] " Michael S. Tsirkin
2023-09-04 7:46 ` [virtio-dev] Re: [virtio-comment] " Xuan Zhuo
2023-09-04 7:33 ` [virtio-dev] Re: " Xuan Zhuo
2023-09-04 8:00 ` [virtio-dev] " Parav Pandit
2023-09-04 8:02 ` [virtio-dev] " Xuan Zhuo
2023-09-04 8:08 ` [virtio-dev] " Parav Pandit
2023-09-04 8:52 ` [virtio-dev] " Xuan Zhuo
2023-09-04 10:26 ` [virtio-dev] " Parav Pandit
2023-09-04 11:11 ` Heng Qi
2023-09-04 12:21 ` Parav Pandit
2023-09-04 13:28 ` Michael S. Tsirkin [this message]
2023-09-04 13:40 ` Parav Pandit
2023-09-05 2:55 ` Xuan Zhuo
2023-09-05 3:31 ` Parav Pandit
2023-09-05 6:42 ` Xuan Zhuo
2023-09-05 6:51 ` Parav Pandit
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=20230904092711-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.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