From: Rick Jones <rick.jones2@hp.com>
To: Florian Westphal <fw@strlen.de>, netdev@vger.kernel.org
Cc: Neal Cardwell <ncardwell@google.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
Yuchung Cheng <ycheng@google.com>
Subject: Re: [PATCH next resend] tcp: use zero-window when free_space is low
Date: Thu, 13 Feb 2014 09:18:36 -0800 [thread overview]
Message-ID: <52FCFE6C.4060002@hp.com> (raw)
In-Reply-To: <1392292350-28800-1-git-send-email-fw@strlen.de>
On 02/13/2014 03:52 AM, Florian Westphal wrote:
> Maybe someone has better idea?
Does tcp_rmem have to be a "hard" limit, or could it allowed to be fuzzy?
rick jones
next prev parent reply other threads:[~2014-02-13 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 11:52 [PATCH next resend] tcp: use zero-window when free_space is low Florian Westphal
2014-02-13 14:58 ` Eric Dumazet
2014-02-13 15:34 ` Florian Westphal
2014-02-13 16:19 ` Eric Dumazet
2014-02-13 17:18 ` Rick Jones [this message]
2014-02-17 19:34 ` David Miller
2014-02-17 20:52 ` Florian Westphal
2014-02-18 17:30 ` Eric Dumazet
2014-02-18 23:12 ` Eric Dumazet
2014-02-19 21:36 ` 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=52FCFE6C.4060002@hp.com \
--to=rick.jones2@hp.com \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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).