netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Timo Teräs" <timo.teras@iki.fi>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, herbert@gondor.apana.org.au,
	kuznet@ms2.inr.ac.ru
Subject: Re: ip_gre headroom allocation
Date: Thu, 11 Jun 2009 13:17:14 +0300	[thread overview]
Message-ID: <4A30D9AA.1020004@iki.fi> (raw)
In-Reply-To: <20090611.030922.91415233.davem@davemloft.net>

David Miller wrote:
> From: Timo Teräs <timo.teras@iki.fi>
> Date: Thu, 11 Jun 2009 11:22:34 +0300
> 
>> I'm not entirely sure about this, but shouldn't we do something like
>> the below to make ip_gre allocation enough headroom for paths where
>> e.g. xfrm transformations take place (as a speed optimization)?
> 
> This should be handled by the code one level up that allocates
> the SKB.
> 
> And as routes get stacked, the MTUs and headroom values get adjusted
> up to the root.
> 
> At least that's how it's supposed to work :-)

Ok, that makes sense. I was just wondering if there's any corner cases
were this would have helped.

> Otherwise we'd need a similar hack in ipip.c too.

I was under the impression that as we need to do the route lookup anyway
we could take advantage of the information available from there fully.

But yes, your explanation makes perfect sense.

Thanks,
  Timo


  reply	other threads:[~2009-06-11 10:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  8:22 ip_gre headroom allocation Timo Teräs
2009-06-11 10:09 ` David Miller
2009-06-11 10:17   ` Timo Teräs [this message]
2009-06-11 10:56     ` Herbert Xu
2009-06-11 11:29       ` Timo Teräs
2009-06-11 11:37         ` Herbert Xu
2009-06-11 11:51           ` Timo Teräs
2009-06-11 12:12             ` Herbert Xu

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=4A30D9AA.1020004@iki.fi \
    --to=timo.teras@iki.fi \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.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 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).