From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Network Development <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: TCP transmit performance regression
Date: Tue, 10 Jul 2012 10:28:28 +0200 [thread overview]
Message-ID: <1341908908.3265.4508.camel@edumazet-glaptop> (raw)
In-Reply-To: <CACVXFVPgqtSN3BrEXRxSv4yxaxCni495SxZNXBmYQpagmxk2tQ@mail.gmail.com>
On Tue, 2012-07-10 at 15:22 +0800, Ming Lei wrote:
> Kernel stack size is 8KB or more, so could you find process creation failure
> in your ChromeBooks machine at the same time?
I believe you mix a lot of things.
Have you ever heard of sockets limits ?
All available ram on a machine is not for whoever wants it, thanks God.
No : TCP stack was dropping frames, because of socket limits.
Only because skbs were fat (8KB allocated/truesize, for a single 1500
bytes frame)
If application is fast and read skb as soon as the arrive, no problem is
detected.
But if application is slow, or a TCP packet is lost on network,
man packets are queued into ofo queue. And eventually not enough room is
avalable -> we drop incoming frames, and sender has to restransmit them.
So instead of loading your web pages as fast as possible, you have to
wait for retransmits.
So you see nothing at all, no kernel logs, no failed memory attempts.
Only its slower than necessary
next prev parent reply other threads:[~2012-07-10 8:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 1:45 TCP transmit performance regression Ming Lei
2012-07-05 7:43 ` Eric Dumazet
2012-07-05 8:27 ` Ming Lei
2012-07-05 8:33 ` Eric Dumazet
2012-07-05 8:42 ` Ming Lei
2012-07-05 9:49 ` Eric Dumazet
2012-07-05 10:02 ` David Miller
2012-07-05 10:32 ` Ming Lei
2012-07-05 10:41 ` Eric Dumazet
2012-07-05 14:01 ` Ming Lei
2012-07-05 14:28 ` Eric Dumazet
2012-07-05 14:56 ` Eric Dumazet
2012-07-06 0:45 ` Ming Lei
2012-07-06 4:58 ` Eric Dumazet
2012-07-06 5:16 ` Eric Dumazet
2012-07-09 5:13 ` Ming Lei
2012-07-09 13:23 ` Ming Lei
2012-07-09 13:54 ` Eric Dumazet
[not found] ` <CACVXFVNdiwVn1Mo--N4N0HdYrEJizExtd_cppT4tS=mjog2PKw@mail.gmail.com>
[not found] ` <1341895143.3265.4049.camel@edumazet-glaptop>
2012-07-10 7:22 ` Ming Lei
2012-07-10 8:28 ` Eric Dumazet [this message]
2012-07-10 13:37 ` Ming Lei
2012-07-10 14:02 ` Eric Dumazet
2012-07-10 14:22 ` Ming Lei
2012-07-10 14:45 ` Eric Dumazet
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=1341908908.3265.4508.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tom.leiming@gmail.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