From: David Chinner <dgc@sgi.com>
To: Cosmo Nova <cs_mcc98@hotmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: file system defragmentation
Date: Tue, 18 Jul 2006 00:19:17 +1000 [thread overview]
Message-ID: <20060717141917.GY2114946@melbourne.sgi.com> (raw)
In-Reply-To: <5356806.post@talk.nabble.com>
On Mon, Jul 17, 2006 at 12:36:09AM -0700, Cosmo Nova wrote:
>
> Hi, you mentioned delayed allocation. What is the size of the buffer holding
> the data, before they're actually written to disk? How can it tackle growing
> files?
No special buffering is needed in XFS as the page cache does it all for us.
delalloc means that XFS does not allocate until the data gets written to disk
(i.e. flushed from the cache). The size of the allocation is dependent on the
amount of contiguous dirty data in the file. That is, The more sequential
dirty pages in the page cache for a file, the larger the allocation...
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2006-07-17 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4f52331f050826001612f8e323@mail.gmail.com>
[not found] ` <20050826101131.GA24544@ii.uib.no>
[not found] ` <4f52331f0508260848782f240a@mail.gmail.com>
[not found] ` <43128F82.4010004@tlinx.org>
[not found] ` <4312913F.6040205@coremetrics.com>
[not found] ` <43311567.3060208@tlinx.org>
2006-07-17 7:36 ` file system defragmentation Cosmo Nova
2006-07-17 9:32 ` David Chatterton
2006-07-17 14:19 ` David Chinner [this message]
2006-07-18 7:59 ` Cosmo Nova
2006-07-18 21:33 ` Chris Wedgwood
2006-07-19 10:33 ` Cosmo Nova
2006-07-17 19:08 ` Chris Wedgwood
[not found] ` <E4E12CD035E14A4AB8C36E0F4B7143F7277DED@iu-mssg-mbx09.exchange.iu.edu>
[not found] ` <43112C5D.8090202@sgi.com>
[not found] ` <20050829001723.GA10587@xiao.rsnet>
2006-07-20 4:22 ` Cosmo Nova
[not found] ` <20050828034108.73921.qmail@web34103.mail.mud.yahoo.com>
2006-07-20 4:23 ` Cosmo Nova
2006-08-08 23:34 ` 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=20060717141917.GY2114946@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=cs_mcc98@hotmail.com \
--cc=linux-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