netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Daniel Lezcano <daniel.lezcano@free.fr>
Cc: David Miller <davem@davemloft.net>,
	eric.dumazet@gmail.com, kaber@trash.net, nightnord@gmail.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH][v3] dev : fix mtu check when TSO is enabled
Date: Tue, 15 Mar 2011 11:17:56 -0700	[thread overview]
Message-ID: <20110315111756.64b5f4b1@nehalam> (raw)
In-Reply-To: <4D7F7054.70409@free.fr>

On Tue, 15 Mar 2011 14:57:40 +0100
Daniel Lezcano <daniel.lezcano@free.fr> wrote:

> On 03/15/2011 12:59 AM, David Miller wrote:
> > From: Daniel Lezcano<daniel.lezcano@free.fr>
> > Date: Mon, 14 Mar 2011 21:39:50 +0100
> >
> >> +	len = dev->mtu + dev->hard_header_len + VLAN_HLEN;
> >> +	if (skb->len<  len)
> >> +		return true;
> > This is not a correct translation of the original test:
> >
> >> -		     (skb->len>  (dev->mtu + dev->hard_header_len + VLAN_HLEN)))) {
> > You need to use "<=" in your version, which currently rejects all
> > full sized frames. :-)
> 
> Right, thanks.
> 
> >> +
> >> +	/* if TSO is enabled, we don't care about the length as the packet
> >> +	 * could be forwarded without being segmented before
> >> +	 */
> >> +	if (skb->dev&&  skb->dev->features&  NETIF_F_TSO)
> >> +		return true;
> > I am trying to understand why you aren't simply checking also if this
> > is a segmented frame?  Perhaps skb_is_gso()&&  device has NETIF_F_TSO
> > set?
> 
> Maybe I am misunderstanding but the packet was forwarded by another device.
> In our case from macvlan:
> 
> macvlan_start_xmit
>      macvlan_queue_xmit
>          dest->forward
>              dev_skb_forward
> 
> When we reached dev_skb_forward, that means we passed through 
> dev_hard_start_xmit where the packet was already segmented so we should 
> exit at the first test (skb->len < len). I don't see the point of adding 
> the skb_is_gso.
> But maybe I am missing something, can you explain ?

The macvlan device only has one downstream device (slave).
If kernel is working properly, macvlan device should have a subset
of the features of the underlying device and macvlan device should
have same MTU as underlying device. If the feature/MTU flags
were correct, then the path calling macvlan should be respecting
the MTU.



-- 

  reply	other threads:[~2011-03-15 18:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 20:39 [PATCH][v3] dev : fix mtu check when TSO is enabled Daniel Lezcano
2011-03-14 23:59 ` David Miller
2011-03-15 13:57   ` Daniel Lezcano
2011-03-15 18:17     ` Stephen Hemminger [this message]
2011-03-16 13:56       ` Daniel Lezcano
2011-03-16 15:35         ` Stephen Hemminger
2011-03-16 16:19           ` Daniel Lezcano
2011-03-16 16:45             ` Stephen Hemminger
2011-03-21 22:58               ` Eric W. Biederman
2011-03-22  2:31                 ` Jesse Gross
2011-03-22  3:02                   ` Eric W. Biederman
2011-03-22  0:05   ` Michał Mirosław

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=20110315111756.64b5f4b1@nehalam \
    --to=shemminger@vyatta.com \
    --cc=daniel.lezcano@free.fr \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=nightnord@gmail.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;
as well as URLs for NNTP newsgroup(s).