public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nscott@aconex.com>
To: David Chinner <dgc@sgi.com>
Cc: lord@xfs.org, xfs@oss.sgi.com
Subject: Re: Directories > 2GB
Date: Tue, 10 Oct 2006 12:07:15 +1000	[thread overview]
Message-ID: <1160446035.8366.42.camel@edge> (raw)
In-Reply-To: <20061010015512.GQ11034@melbourne.sgi.com>

On Tue, 2006-10-10 at 11:55 +1000, David Chinner wrote:
> On Mon, Oct 09, 2006 at 04:53:02PM -0500, Steve Lord wrote:
> > You might want to think about keeping the directory a little
> > more contiguous than individual disk blocks. XFS does have
> > code in it to allocate the directory in chunks larger than
> > a single file system block. It does not get used on linux
> > because the code was written under the assumption you can
> > see the whole chunk as a single piece of memory which does not
> > work to well in the linux kernel.
> 
> This code is enabled and seems to work in Linux. I don't know if it
> passes xfsqa  so I don't know how reliable this feature is.

It did at one point - though I've not tested that combination for
awhile, I expect it will still work fine.  It should - the
artist-formerly-known-as-pagebuf does handle multiple discontiguous
pages, and the dir2 code is using that memory in a way thats going
to work correctly, IIRC.

cheer

-- 
Nathan

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04 16:56 Directories > 2GB Andreas Dilger
2006-10-04 17:51 ` Dave Kleikamp
2006-10-04 19:09 ` Peter Grandi
2006-10-09 21:53 ` Steve Lord
2006-10-10  1:55   ` David Chinner
2006-10-10  2:07     ` Nathan Scott [this message]
2006-10-10  2:15     ` Steve Lord
2006-10-10  9:19       ` Christoph Hellwig
2006-10-10 23:31         ` David Chinner
2006-10-11 16:49           ` Steve Lord
2006-10-12  0:26             ` David Chinner

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=1160446035.8366.42.camel@edge \
    --to=nscott@aconex.com \
    --cc=dgc@sgi.com \
    --cc=lord@xfs.org \
    --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