From: Eric Dumazet <eric.dumazet@gmail.com>
To: Sylvain Munaut <s.munaut@whatever-company.com>
Cc: netdev@vger.kernel.org
Subject: Re: Fwd: TCP fragmentation broken in 3.6-rc ?
Date: Mon, 20 Aug 2012 17:14:30 +0200 [thread overview]
Message-ID: <1345475670.5158.322.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAF6-1L5bnhHfXide-=+4WmskR6xGLg4q+RWHebH+GiX7P-RX+Q@mail.gmail.com>
On Mon, 2012-08-20 at 16:56 +0200, Sylvain Munaut wrote:
> Hi,
>
> It seems somehow something was broken in 3.6-rc.
> I'm not sure exactly what though. The symptoms are:
>
> - TCP connection get "stuck" with data in send queue when doing
> "large" transfers ( like typing 'ps ax' on a ssh connection )
> - Only happens on path where the PMTU is lower than the MTU of the interface
> - Is not present right after boot, it only appears 10-20min after
> boot or so. (and that's inside the _same_ TCP connection, it works
> fine at first and then in the same ssh session, it'll get stuck)
> - Definitely seems related to fragments somehow since I see a router
> sending ICMP message saying fragmentation is needed.
> - Exact same setup works fine with kernel 3.5.1
>
> Cheers,
Could you make sure its not a pfmemalloc problem, by applying following
patch :
https://lkml.org/lkml/2012/8/20/182
Thanks
next prev parent reply other threads:[~2012-08-20 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF6-1L6xy1rRd321ZMzrLG6xHMdO0+sdjbtznUOsMzfYyU1SEg@mail.gmail.com>
2012-08-20 14:56 ` Fwd: TCP fragmentation broken in 3.6-rc ? Sylvain Munaut
2012-08-20 15:14 ` Eric Dumazet [this message]
2012-08-20 15:52 ` Sylvain Munaut
2012-08-20 16:02 ` Eric Dumazet
2012-08-21 11:56 ` Sylvain Munaut
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=1345475670.5158.322.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=s.munaut@whatever-company.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