[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111124010147.GA15318@gondor.apana.org.au>
Date: Thu, 24 Nov 2011 09:01:47 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: David Miller <davem@...emloft.net>
Cc: steffen.klassert@...unet.com, netdev@...r.kernel.org
Subject: Re: [PATCH 5/5] ipv4: Don't use the cached pmtu informations for
input routes
On Wed, Nov 23, 2011 at 07:17:58PM -0500, David Miller wrote:
>
> It means there is a propagation delay of PMTU increasing which is on the
> order of the number of hops between the sender and the PMTU increased link.
> So if the PMTU timeout is X, the propagation time is X * N_HOPS.
That assumes that each router in the path would constantly probe
to refresh its cached value, as otherwise they should all expire
after X.
However, as this was the original behaviour, I think going back to
it is fine.
I am curious in knowing exactly what scenario Steffen ran into
that prompted this change though.
Cheers,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists