From: "David S. Miller" <davem@redhat.com>
To: Ben Greear <greearb@candelatech.com>
Cc: dada1@cosmosbay.com, jun.nakajima@intel.com, ak@muc.de,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: Network buffer hang was Re: [PATCH] 2.6 workaround for Athlon/Opteron prefetch errata
Date: Thu, 11 Sep 2003 18:41:03 -0700 [thread overview]
Message-ID: <20030911184103.2646b189.davem@redhat.com> (raw)
In-Reply-To: <3F612570.1010303@candelatech.com>
On Thu, 11 Sep 2003 18:46:24 -0700
Ben Greear <greearb@candelatech.com> wrote:
> I was using kernel 2.4.21 or so, and had tcp buffers turned up
> quite high.
You seal your own fate by setting this too high. It's meant
to keep TCP from commiting too much system memory to itself.
prev parent reply other threads:[~2003-09-12 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uqD5.3BI.3@gated-at.bofh.it>
2003-09-11 4:14 ` [PATCH] 2.6 workaround for Athlon/Opteron prefetch errata Andi Kleen
2003-09-11 4:58 ` dada1
2003-09-11 5:11 ` Andi Kleen
2003-09-11 5:58 ` dada1
2003-09-11 12:09 ` Network buffer hang was " Andi Kleen
2003-09-11 13:17 ` dada1
2003-09-12 1:46 ` Ben Greear
2003-09-12 1:41 ` David S. Miller [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=20030911184103.2646b189.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@muc.de \
--cc=dada1@cosmosbay.com \
--cc=greearb@candelatech.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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).