public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet•com>
To: Hannes Frederic Sowa <hannes@stressinduktion•org>,
	netdev@vger•kernel.org, eric.dumazet@gmail•com,
	davem@davemloft•net
Subject: Re: [PATCH net-next 1/2] ipv4: add forwarding_uses_pmtu knob to protect forward path to use pmtu info
Date: Mon, 6 Jan 2014 14:18:22 +0100	[thread overview]
Message-ID: <20140106131822.GU31491@secunet.com> (raw)
In-Reply-To: <20140106090521.GQ31491@secunet.com>

On Mon, Jan 06, 2014 at 10:05:21AM +0100, Steffen Klassert wrote:
> > 
> > IIRC you have a (semi-)automatic test suite to test for (p)mtu problems? Would
> > these checks cover such a change?
> > 
> 
> I'm currenlty testing these patches. ipv4 looks good but on
> ipv6 with 'ping6' the packet size is not reduced according
> to the pmtu when forward_use_pmtu is set to 0.
> 
> I'll run the tests again with your updated v3 patches.
> 

The v3 version of your patches don't show any obvious regressions
on our pmtu test suite.

  parent reply	other threads:[~2014-01-06 13:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 13:08 [PATCH net-next 1/2] ipv4: add forwarding_uses_pmtu knob to protect forward path to use pmtu info Hannes Frederic Sowa
2013-12-31  3:20 ` David Miller
2013-12-31  3:52   ` Hannes Frederic Sowa
2013-12-31  6:04     ` David Miller
2013-12-31  7:02       ` Hannes Frederic Sowa
2013-12-31 17:59         ` John Heffner
2013-12-31 18:41           ` Hannes Frederic Sowa
2014-01-05 10:41   ` Hannes Frederic Sowa
2014-01-05 19:45     ` David Miller
2013-12-31  4:28 ` Hannes Frederic Sowa
2014-01-06  9:05   ` Steffen Klassert
2014-01-06  9:14     ` Hannes Frederic Sowa
2014-01-06 13:18     ` Steffen Klassert [this message]
2014-01-06 13:29       ` Hannes Frederic Sowa

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=20140106131822.GU31491@secunet.com \
    --to=steffen.klassert@secunet$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=eric.dumazet@gmail$(echo .)com \
    --cc=hannes@stressinduktion$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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