From: "David S. Miller" <davem@davemloft.net>
To: Baruch Even <baruch@ev-en.org>
Cc: netdev@oss.sgi.com, shemminger@osdl.org
Subject: Re: TCP performance drop 2.6.6->2.6.7
Date: Tue, 12 Apr 2005 15:47:28 -0700 [thread overview]
Message-ID: <20050412154728.463e3d10.davem@davemloft.net> (raw)
In-Reply-To: <425C493B.5040206@ev-en.org>
On Tue, 12 Apr 2005 23:18:35 +0100
Baruch Even <baruch@ev-en.org> wrote:
> I was wondering if someone can think of a reason why this happens?
Probably some bug we fixed in 2.6.8 or later...
> Is there a way to get the different network related patches between
> these two versions? I don't have access to bk to get it myself.
Get patch-2.6.7.bz2 or whatever from kernel.org, then scan around for
changes to include/*/tcp.h and net/ipv4/tcp*.c
next prev parent reply other threads:[~2005-04-12 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 22:18 TCP performance drop 2.6.6->2.6.7 Baruch Even
2005-04-12 22:47 ` David S. Miller [this message]
2005-04-12 23:07 ` Stephen Hemminger
2005-04-12 23:59 ` Baruch Even
2005-04-13 18:20 ` Stephen Hemminger
2005-04-15 14:37 ` Baruch Even
2005-04-15 15:30 ` Nivedita Singhvi
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=20050412154728.463e3d10.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=baruch@ev-en.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).