From: Hagen Paul Pfeifer <hagen@jauu.net>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: David Miller <davem@davemloft.net>, <roel.kluin@gmail.com>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [TCP]: min_t/max_t confusion in tcp_select_initial_window()?
Date: Wed, 18 Aug 2010 16:09:30 +0200 [thread overview]
Message-ID: <93bf5f79c0e69b1853298bbce1876b5b@localhost> (raw)
In-Reply-To: <alpine.DEB.2.00.0912232321090.10866@melkinpaasi.cs.helsinki.fi>
On Wed, 23 Dec 2009 23:23:11 +0200 (EET), "Ilpo Järvinen" wrote:
> Yeah, I'm wrong, and besides misread your "It looks correct" to mean the
> proposed change rather than the current code.
But the code is not correct if we consider reduced buffers via
setsockopt(), some days ago I sent a patch to fix the problem.
Ilpo? David?
Hagen
prev parent reply other threads:[~2010-08-18 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 2:00 [TCP]: min_t/max_t confusion in tcp_select_initial_window()? Roel Kluin
2009-12-23 3:47 ` David Miller
2009-12-23 19:45 ` Ilpo Järvinen
2009-12-23 21:15 ` David Miller
2009-12-23 21:23 ` Ilpo Järvinen
2010-08-18 14:09 ` Hagen Paul Pfeifer [this message]
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=93bf5f79c0e69b1853298bbce1876b5b@localhost \
--to=hagen@jauu.net \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
--cc=roel.kluin@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;
as well as URLs for NNTP newsgroup(s).