From: Christoph Lameter <clameter@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: Nathan Scott <nathans@sgi.com>, Andrew Morton <akpm@osdl.org>,
nickpiggin@yahoo.com.au, linux-mm@kvack.org,
dgc@melbourne.sgi.com
Subject: Re: Avoid excessive time spend on concurrent slab shrinking
Date: Sat, 1 Apr 2006 10:49:14 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0604011047340.11929@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20060401183038.GY27189130@melbourne.sgi.com>
On Sun, 2 Apr 2006, David Chinner wrote:
> same hash chain, which tends to implicate not enough hash buckets.
>
> > If its useful for experimenting, Christoph, you can easily tweak the
> > cluster hash size manually by dinking with xfs_iget.c::xfs_chash_init.
>
> Just use the ihashsize mount option - the cluster hash size is proportional
> to the inode hash size which is changed by the ihashsize mount option.
>
> Cheers,
XFS settings visible via /proc/mounts are
rw,ihashsize=32768,sunit=32,swidth=25
Not enough hash buckets? This was the default selection by xfs.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-04-01 18:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 22:44 Christoph Lameter
[not found] ` <20060331150120.21fad488.akpm@osdl.org>
2006-03-31 23:17 ` Christoph Lameter
2006-03-31 23:46 ` Andrew Morton
[not found] ` <20060331153235.754deb0c.akpm@osdl.org>
2006-03-31 23:48 ` Christoph Lameter
2006-04-01 0:00 ` Andrew Morton
2006-04-01 0:14 ` Andrew Morton
2006-04-01 0:22 ` Christoph Lameter
2006-04-01 1:25 ` Andrew Morton
2006-04-01 2:34 ` Nick Piggin
2006-04-01 5:59 ` Nathan Scott
2006-04-01 18:30 ` David Chinner
2006-04-01 18:49 ` Christoph Lameter [this message]
2006-04-01 18:24 ` David Chinner
2006-03-31 23:45 ` Andrew Morton
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=Pine.LNX.4.64.0604011047340.11929@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@osdl.org \
--cc=dgc@melbourne.sgi.com \
--cc=dgc@sgi.com \
--cc=linux-mm@kvack.org \
--cc=nathans@sgi.com \
--cc=nickpiggin@yahoo.com.au \
/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