From: Rusty Russell <rusty@rustcorp.com.au>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 2/3] virtio: Net header needs gso_hdr_len
Date: Wed, 23 Jan 2008 09:06:14 +1100 [thread overview]
Message-ID: <200801230906.14585.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080122103630.GA24135@gondor.apana.org.au>
On Tuesday 22 January 2008 21:36:30 Herbert Xu wrote:
> On Wed, Jan 16, 2008 at 03:19:03PM +1100, Rusty Russell wrote:
> > > > It's far easier to deal with GSO if we don't have to parse the packet
> > > > to figure out the header length. Add the field to the virtio_net_hdr
> > > > struct (and fix the spaces that somehow crept in there).
> > >
> > > Why do we need this? When receiving GSO packets from an untrusted
> > > source the network stack will fill in the transport header offset
> > > after verifying that the headers are sane.
> >
> > Thanks for clarifying; it simplifies things.
>
> Actually now that I've tried your test program I can see that this
> field exists not because of GSO, but because of SG. It tells you
> how many bytes you want to put in the skb head as opposed to the
> frag array.
Yes, I took it out after your comments, then realized I needed it and put it
back.
> So this field is fine with me as long as it is named as such to
> avoid confusion since it really has nothing to do with GSO as you
> also need it for SG with large MTUs.
Hmm, how about just "hdr_len" rather than "gso_hdr_len"?
Thanks,
Rusty.
next prev parent reply other threads:[~2008-01-22 22:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 10:41 [PATCH 1/3] skb_partial_csum_set Rusty Russell
2008-01-15 10:43 ` [PATCH 2/3] virtio: Net header needs gso_hdr_len Rusty Russell
2008-01-15 10:47 ` [PATCH 3/3] tun/tap GSO/partial csum support Rusty Russell
2008-01-15 10:47 ` Rusty Russell
2008-01-16 0:06 ` [PATCH 2/3] virtio: Net header needs gso_hdr_len Herbert Xu
2008-01-16 4:19 ` Rusty Russell
2008-01-22 10:36 ` Herbert Xu
2008-01-22 22:06 ` Rusty Russell
2008-01-22 22:06 ` Rusty Russell [this message]
2008-01-22 22:29 ` Herbert Xu
2008-01-22 22:29 ` Herbert Xu
2008-01-22 10:36 ` Herbert Xu
2008-01-16 4:19 ` Rusty Russell
2008-01-16 0:06 ` Herbert Xu
2008-01-15 10:43 ` Rusty Russell
2008-01-15 11:14 ` [PATCH 1/3] skb_partial_csum_set David Miller
2008-01-15 11:14 ` David Miller
2008-01-15 21:03 ` Rusty Russell
2008-01-15 21:03 ` Rusty Russell
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=200801230906.14585.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=herbert@gondor.apana.org.au \
--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.