From: "David S. Miller" <davem@redhat.com>
To: jgarzik@mandrakesoft.com
Cc: chris@chrullrich.de, viro@math.psu.edu, torvalds@transmeta.com,
v.sweeney@dexterus.com, arvest@orphansonfire.com,
linux-kernel@vger.kernel.org
Subject: Re: Partitioning problems in 2.4.11
Date: Thu, 11 Oct 2001 16:27:09 -0700 (PDT) [thread overview]
Message-ID: <20011011.162709.39156842.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1011011180912.5934I-100000@mandrakesoft.mandrakesoft.com>
In-Reply-To: <20011012010310.A1255@christian.chrullrich.de> <Pine.LNX.3.96.1011011180912.5934I-100000@mandrakesoft.mandrakesoft.com>
From: Jeff Garzik <jgarzik@mandrakesoft.com>
Date: Thu, 11 Oct 2001 18:10:43 -0500 (CDT)
> Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
To tangent, do we really need a mount cache that big, even on a highmem
machine?
Yes, in fact on machines with 16GB or so of ram we perform poorly due
to the 4MB size restriction from GFP() allocations. Anton Blanchard
hit this on large PPC64 SMP machines already.
On a 16GB or 32GB ram machine, the hash chains go to 20 deep even on
simple benchmarks and all performance goes to the toilet.
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-10-11 23:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 20:00 Partitioning problems in 2.4.11 Alexander Viro
2001-10-11 22:31 ` Christian Ullrich
2001-10-11 22:59 ` Alexander Viro
2001-10-11 23:03 ` Christian Ullrich
2001-10-11 23:10 ` Jeff Garzik
2001-10-11 23:22 ` Alexander Viro
2001-10-11 23:28 ` David S. Miller
2001-10-11 23:27 ` David S. Miller [this message]
2001-10-11 23:34 ` Stephan von Krawczynski
2001-10-11 23:43 ` Alexander Viro
2001-10-11 22:42 ` Alexander Viro
2001-10-11 23:08 ` Christian Ullrich
2001-10-11 23:19 ` Alexander Viro
2001-10-11 23:55 ` [PATCH] " Alexander Viro
2001-10-12 10:19 ` Vincent Sweeney
2001-10-11 23:30 ` Alexander Viro
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=20011011.162709.39156842.davem@redhat.com \
--to=davem@redhat.com \
--cc=arvest@orphansonfire.com \
--cc=chris@chrullrich.de \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=v.sweeney@dexterus.com \
--cc=viro@math.psu.edu \
/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