From: David Miller <davem@davemloft.net>
To: steffen.klassert@secunet.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/5] ipv4: Kill ip_rt_frag_needed().
Date: Wed, 13 Jun 2012 03:22:28 -0700 (PDT) [thread overview]
Message-ID: <20120613.032228.1574539964049471628.davem@davemloft.net> (raw)
In-Reply-To: <20120613100709.GO27795@secunet.com>
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Wed, 13 Jun 2012 12:07:09 +0200
> On Wed, Jun 13, 2012 at 02:42:25AM -0700, David Miller wrote:
>> From: Steffen Klassert <steffen.klassert@secunet.com>
>> Date: Wed, 13 Jun 2012 10:01:52 +0200
>>
>> > I think an application that sets IP_PMTUDISC_WANT explicitly will
>> > rely on the fact that the kernel does pmtu discovery. Changing
>> > the socket setting to IP_PMTUDISC_DONT the first time we get into
>> > trouble makes IP_PMTUDISC_WANT pointless for udp and raw sockets.
>>
>> How so?
>>
>> We are mimicking exactly what would happen if we had just created
>> a new routing cache entry when the application openned the socket.
>>
>> There is no behavioral difference whatsoever.
>>
>> We absolutely do perform PMTU discovery, the first large packet
>> will trigger it. And then, as if we had lowered the PMTU in
>> the routing cache entry, we will stop setting DF in the packets.
>
> Maybe I missunderstood what you meant. I thought that you don't want
> to update the pmtu cache informations at all on udp and raw.
> If we update the pmtu cache informations with first large packet,
> I agree absolutely.
We don't update the PMTU.
But we behave as if we did.
The only effect the IP_PMTUDISC_* values have is in deciding whether
to set the DF flag in the outgoing packets.
next prev parent reply other threads:[~2012-06-13 10:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 9:29 [PATCH 2/5] ipv4: Kill ip_rt_frag_needed() David Miller
2012-06-11 11:16 ` Steffen Klassert
2012-06-11 11:20 ` David Miller
2012-06-11 11:28 ` David Miller
2012-06-11 11:42 ` Steffen Klassert
2012-06-11 23:02 ` David Miller
2012-06-12 11:44 ` Steffen Klassert
2012-06-12 20:33 ` David Miller
2012-06-13 4:22 ` David Miller
2012-06-13 8:01 ` Steffen Klassert
2012-06-13 9:42 ` David Miller
2012-06-13 10:07 ` Steffen Klassert
2012-06-13 10:22 ` David Miller [this message]
2012-06-14 5:35 ` Steffen Klassert
2012-06-14 5:42 ` David Miller
2012-06-14 5:58 ` Steffen Klassert
2012-06-14 5:59 ` David Miller
2012-06-14 6:36 ` Steffen Klassert
2012-06-14 6:54 ` David Miller
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=20120613.032228.1574539964049471628.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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).