From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH net] virtio-net: unbreak cusmed packet for small buffer XDP
Date: Wed, 28 Jun 2017 07:01:00 +0300 [thread overview]
Message-ID: <20170628065126-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <51f4c402-6a02-9bad-6dab-563ca72f431a@redhat.com>
On Wed, Jun 28, 2017 at 11:40:30AM +0800, Jason Wang wrote:
>
>
> On 2017年06月28日 11:31, Michael S. Tsirkin wrote:
> > On Wed, Jun 28, 2017 at 10:45:18AM +0800, Jason Wang wrote:
> > > On 2017年06月28日 10:17, Michael S. Tsirkin wrote:
> > > > On Wed, Jun 28, 2017 at 10:14:34AM +0800, Jason Wang wrote:
> > > > > On 2017年06月28日 10:02, Michael S. Tsirkin wrote:
> > > > > > On Wed, Jun 28, 2017 at 09:54:03AM +0800, Jason Wang wrote:
> > > > > > > We should allow csumed packet for small buffer, otherwise XDP_PASS
> > > > > > > won't work correctly.
> > > > > > >
> > > > > > > Fixes commit bb91accf2733 ("virtio-net: XDP support for small buffers")
> > > > > > > Signed-off-by: Jason Wang<jasowang@redhat.com>
> > > > > > The issue would be VIRTIO_NET_HDR_F_DATA_VALID might be set.
> > > > > > What do you think?
> > > > > I think it's safe. For XDP_PASS, it work like in the past.
> > > > That's the part I don't get. With DATA_VALID csum in packet is wrong, XDP
> > > > tools assume it's value.
> > > DATA_VALID is CHECKSUM_UNCESSARY on the host, and according to the comment
> > > in skbuff.h
> > >
> > >
> > > "
> > > * The hardware you're dealing with doesn't calculate the full checksum
> > > * (as in CHECKSUM_COMPLETE), but it does parse headers and verify
> > > checksums
> > > * for specific protocols. For such packets it will set
> > > CHECKSUM_UNNECESSARY
> > > * if their checksums are okay. skb->csum is still undefined in this case
> > > * though. A driver or device must never modify the checksum field in the
> > > * packet even if checksum is verified.
> > > "
> > >
> > > The csum is correct I believe?
> > >
> > > Thanks
> > That's on input. But I think for tun it's output, where that is equivalent
> > to CHECKSUM_NONE
> >
> >
>
> Yes, but the comment said:
>
> "
> CKSUM_NONE:
> *
> * The skb was already checksummed by the protocol, or a checksum is not
> * required.
> *
> * CHECKSUM_UNNECESSARY:
> *
> * This has the same meaning on as CHECKSUM_NONE for checksum offload on
> * output.
> *
> "
>
> So still correct I think?
>
> Thanks
Hmm maybe I mean NEEDS_CHECKSUM actually.
I'll need to re-read the spec.
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] virtio-net: unbreak cusmed packet for small buffer XDP
Date: Wed, 28 Jun 2017 07:01:00 +0300 [thread overview]
Message-ID: <20170628065126-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <51f4c402-6a02-9bad-6dab-563ca72f431a@redhat.com>
On Wed, Jun 28, 2017 at 11:40:30AM +0800, Jason Wang wrote:
>
>
> On 2017年06月28日 11:31, Michael S. Tsirkin wrote:
> > On Wed, Jun 28, 2017 at 10:45:18AM +0800, Jason Wang wrote:
> > > On 2017年06月28日 10:17, Michael S. Tsirkin wrote:
> > > > On Wed, Jun 28, 2017 at 10:14:34AM +0800, Jason Wang wrote:
> > > > > On 2017年06月28日 10:02, Michael S. Tsirkin wrote:
> > > > > > On Wed, Jun 28, 2017 at 09:54:03AM +0800, Jason Wang wrote:
> > > > > > > We should allow csumed packet for small buffer, otherwise XDP_PASS
> > > > > > > won't work correctly.
> > > > > > >
> > > > > > > Fixes commit bb91accf2733 ("virtio-net: XDP support for small buffers")
> > > > > > > Signed-off-by: Jason Wang<jasowang@redhat.com>
> > > > > > The issue would be VIRTIO_NET_HDR_F_DATA_VALID might be set.
> > > > > > What do you think?
> > > > > I think it's safe. For XDP_PASS, it work like in the past.
> > > > That's the part I don't get. With DATA_VALID csum in packet is wrong, XDP
> > > > tools assume it's value.
> > > DATA_VALID is CHECKSUM_UNCESSARY on the host, and according to the comment
> > > in skbuff.h
> > >
> > >
> > > "
> > > * The hardware you're dealing with doesn't calculate the full checksum
> > > * (as in CHECKSUM_COMPLETE), but it does parse headers and verify
> > > checksums
> > > * for specific protocols. For such packets it will set
> > > CHECKSUM_UNNECESSARY
> > > * if their checksums are okay. skb->csum is still undefined in this case
> > > * though. A driver or device must never modify the checksum field in the
> > > * packet even if checksum is verified.
> > > "
> > >
> > > The csum is correct I believe?
> > >
> > > Thanks
> > That's on input. But I think for tun it's output, where that is equivalent
> > to CHECKSUM_NONE
> >
> >
>
> Yes, but the comment said:
>
> "
> CKSUM_NONE:
> *
> * The skb was already checksummed by the protocol, or a checksum is not
> * required.
> *
> * CHECKSUM_UNNECESSARY:
> *
> * This has the same meaning on as CHECKSUM_NONE for checksum offload on
> * output.
> *
> "
>
> So still correct I think?
>
> Thanks
Hmm maybe I mean NEEDS_CHECKSUM actually.
I'll need to re-read the spec.
--
MST
next prev parent reply other threads:[~2017-06-28 4:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 1:54 [PATCH net] virtio-net: unbreak cusmed packet for small buffer XDP Jason Wang
2017-06-28 1:54 ` Jason Wang
2017-06-28 2:02 ` Michael S. Tsirkin
2017-06-28 2:02 ` Michael S. Tsirkin
2017-06-28 2:14 ` Jason Wang
2017-06-28 2:14 ` Jason Wang
2017-06-28 2:17 ` Michael S. Tsirkin
2017-06-28 2:17 ` Michael S. Tsirkin
2017-06-28 2:45 ` Jason Wang
2017-06-28 2:45 ` Jason Wang
2017-06-28 3:31 ` Michael S. Tsirkin
2017-06-28 3:31 ` Michael S. Tsirkin
2017-06-28 3:40 ` Jason Wang
2017-06-28 3:40 ` Jason Wang
2017-06-28 4:01 ` Michael S. Tsirkin [this message]
2017-06-28 4:01 ` Michael S. Tsirkin
2017-06-28 12:05 ` Jason Wang
2017-06-28 12:05 ` Jason Wang
2017-07-03 17:03 ` Michael S. Tsirkin
2017-07-03 17:03 ` Michael S. Tsirkin
2017-07-04 12:20 ` Jason Wang
2017-07-04 12:20 ` Jason Wang
2017-07-06 0:07 ` Michael S. Tsirkin
2017-07-06 0:07 ` 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=20170628065126-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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.