From: Andi Kleen <ak@muc.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Really slow netstat and /proc/net/tcp in 2.4
Date: 13 Oct 2001 18:07:43 +0200 [thread overview]
Message-ID: <k2adyvjzg0.fsf@zero.aec.at> (raw)
In-Reply-To: <Pine.LNX.4.21.0110131537470.931-100000@localhost.localdomain>
In-Reply-To: Hugh Dickins's message of "Sat, 13 Oct 2001 16:07:12 +0100 (BST)"
In article <Pine.LNX.4.21.0110131537470.931-100000@localhost.localdomain>,
Hugh Dickins <hugh@veritas.com> writes:
> On Sat, 13 Oct 2001, Andi Kleen wrote:
>>
>> I attached a patch. It allows you to get some simple statistics from
>> /proc/net/sockstat (unfortunately costly too). It also adds a new kernel
>> boot argument tcpehashgoal=order. Order is the log2 of how many pages you
>> want to use for the hash table (so it needs 2^order * 4096 bytes on i386)
>> You can experiment with various sizes and check which one gives still
>> reasonable hash distribution under load.
> Wouldn't something like "tcpehashbuckets" make a better boot tunable
> than "tcpehashorder"? Rounded up to next power of two before used.
[...]
I just hacked something quickly together so that people can test what
impact different hash tables sizes have on their workload, and for
that using the order was easiest. The goal is of course to do
automatic hash table tuning. I don't expect it to be an permanent
tunable. My hope is that it'll turn out that smaller hash tables will
be good enough.
-Andi
prev parent reply other threads:[~2001-10-13 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 18:47 Really slow netstat and /proc/net/tcp in 2.4 Simon Kirby
2001-10-11 19:30 ` kuznet
2001-10-11 19:55 ` Simon Kirby
2001-10-12 16:44 ` kuznet
2001-10-12 19:36 ` Simon Kirby
2001-10-12 19:43 ` kuznet
2001-10-12 19:56 ` Andi Kleen
2001-10-12 22:10 ` Simon Kirby
2001-10-12 23:57 ` Andi Kleen
2001-10-13 15:07 ` Hugh Dickins
2001-10-13 16:07 ` Andi Kleen [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=k2adyvjzg0.fsf@zero.aec.at \
--to=ak@muc.de \
--cc=hugh@veritas.com \
--cc=linux-kernel@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