public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Simon Kirby <sim@netnation.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Awfully slow /proc/net/tcp, netstat, in.identd in 2.4 (updated)
Date: 19 Oct 2001 20:22:21 +0200	[thread overview]
Message-ID: <k23d4fwkv6.fsf@zero.aec.at> (raw)
In-Reply-To: <20011018094222.A31919@netnation.com> <20011019145750.A22193@zero.firstfloor.org> <20011019085944.A16467@netnation.com>
In-Reply-To: Simon Kirby's message of "Fri, 19 Oct 2001 08:59:44 -0700"

In article <20011019085944.A16467@netnation.com>,
Simon Kirby <sim@netnation.com> writes:

> TCP: Hash tables configured (established 262144 bind 65536)

No it means you have 512+k buckets  (*4 on UP; *8 on SMP for bytes = ~4MB) 
for the established hash and 64k for the bind hash (the later is only 
used internally and searched for netstat).

4MB for a hash table looks ridiculously large to me.

> ...but shrinking the size slightly won't really fix the problem, it will
> just make it less obvious.

the size is the problem. walking an 4MB table will be always slow.

-Andi

  reply	other threads:[~2001-10-19 18:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 16:42 Awfully slow /proc/net/tcp, netstat, in.identd in 2.4 (updated) Simon Kirby
2001-10-18 16:49 ` David S. Miller
2001-10-18 17:05   ` Simon Kirby
2001-10-19 12:57 ` Andi Kleen
2001-10-19 15:59   ` Simon Kirby
2001-10-19 18:22     ` Andi Kleen [this message]
2001-10-19 20:59       ` David S. Miller
2001-10-19 21:30         ` Benjamin LaHaise
2001-10-19 21:56           ` David S. Miller
2001-10-19 22:04             ` Benjamin LaHaise
2001-10-19 22:11               ` David S. Miller
2001-10-19 22:13                 ` Benjamin LaHaise

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=k23d4fwkv6.fsf@zero.aec.at \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sim@netnation.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