public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Nathan Scott <nathans@sgi.com>
Cc: vapo@melbourne.sgi.com, xfs@oss.sgi.com
Subject: Re: review: increase bulkstat readahead window
Date: Tue, 25 Jul 2006 10:40:04 +0100	[thread overview]
Message-ID: <20060725094004.GB29615@infradead.org> (raw)
In-Reply-To: <20060725135004.E2116482@wobbly.melbourne.sgi.com>

On Tue, Jul 25, 2006 at 01:50:04PM +1000, Nathan Scott wrote:
> Hi all,
>     
> We limit the amount of bulkstat readahead we can issue based on 
> the size of the array of inode cluster records (irbuf), which we
> allocate on each bulkstat call.  Increasing the size of this array
> has shown noticable performance improvements, and given bulkstat
> is always called to scan the filesystem from one end to the other,
> we're going to have to issue that IO at some point, may as well do
> it up front.  We don't want to get silly in sizing this buffer, 
> though, as it needs to be a contiguous chunk of memory.  Here I've
> increased it from 1 page to 4 pages, with some logic to halve the
> size incrementally if we cant allocate that successfully (as we do
> in one or two other places in XFS, for other things).

ok.  I wonder whether we should add a generic kmalloc_leastmost routine
(with a name better than that of course..)

  reply	other threads:[~2006-07-25 10:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-25  3:50 review: increase bulkstat readahead window Nathan Scott
2006-07-25  9:40 ` Christoph Hellwig [this message]
2006-07-25 22:37   ` Nathan Scott
2006-07-26 10:25     ` Christoph Hellwig
2006-07-27 23:17       ` Nathan Scott
2006-07-28  1:58         ` Review: xfs_repair fixes for dir2 corruption Barry Naujok
2006-07-28  8:10           ` Nathan Scott
2006-07-28 14:45             ` Madan Valluri
2006-07-31  7:18               ` Barry Naujok
2006-07-30  5:19           ` christian
2006-08-01 21:50           ` Adam Sjøgren
2006-08-01 23:06             ` Christian Guggenberger

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=20060725094004.GB29615@infradead.org \
    --to=hch@infradead.org \
    --cc=nathans@sgi.com \
    --cc=vapo@melbourne.sgi.com \
    --cc=xfs@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