From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: reduce memory needs of out of order queue
Date: Fri, 14 Oct 2011 19:33:04 +0200 [thread overview]
Message-ID: <1318613584.2223.53.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <1318579509.2533.110.camel@edumazet-laptop>
Le vendredi 14 octobre 2011 à 10:05 +0200, Eric Dumazet a écrit :
> This patch specifically addresses the OFO problem, trying to lower
> memory usage for machines handling lot of sockets (proxies for example)
Well, thinking a bit more about it is needed, so zap the patch please.
Thanks
next prev parent reply other threads:[~2011-10-14 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 7:19 [PATCH net-next] tcp: reduce memory needs of out of order queue Eric Dumazet
2011-10-14 7:42 ` David Miller
2011-10-14 8:05 ` Eric Dumazet
2011-10-14 17:33 ` Eric Dumazet [this message]
2011-10-14 15:50 ` Rick Jones
2011-10-14 16:00 ` Eric Dumazet
2011-10-14 16:11 ` Eric Dumazet
2011-10-14 22:12 ` Rick Jones
2011-10-14 23:18 ` David Miller
2011-10-15 6:54 ` Eric Dumazet
2011-10-17 0:53 ` David Miller
2011-10-17 7:02 ` Eric Dumazet
2011-10-15 6:39 ` Eric Dumazet
2011-10-17 16:47 ` Rick Jones
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=1318613584.2223.53.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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