All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cosmo Nova <cs_mcc98@hotmail.com>
To: linux-xfs@oss.sgi.com
Subject: Re: file system defragmentation
Date: Wed, 19 Jul 2006 03:33:13 -0700 (PDT)	[thread overview]
Message-ID: <5393901.post@talk.nabble.com> (raw)
In-Reply-To: <20060718213304.GA27287@tuatara.stupidest.org>


If there are AG locks, but multiple files can write in the same AG, how "AG
lock" is interpreted by XFS then? What does it really do?

For pre-allocation and delayed allocation, do they belong to the feature set
of XFS? Or are they application dependant?

I am trying to compare filesystems, especially xfs vs jfs. I found that
jfs's per AG locking would only allow one file to be written per AG, which
helps a lot to prevent fragmentation (according to experiment results).
There're no pre-allocation and delayed allocation in JFS though. Comparing
the experiment results, XFS is doing a good job, giving 6-10 fragments
(compare to majority of single fragment in JFS...). So answers of the above
questions with numbers would help a lot. Thanks!
-- 
View this message in context: http://www.nabble.com/file-system-defragmentation-tf255485.html#a5393901
Sent from the Xfs - General forum at Nabble.com.

  reply	other threads:[~2006-07-19 10:33 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
2006-07-18  7:59               ` Cosmo Nova
2006-07-18 21:33                 ` Chris Wedgwood
2006-07-19 10:33                   ` Cosmo Nova [this message]
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=5393901.post@talk.nabble.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.