All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Smit Shah <getsmit@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: XFS Preallocate using ALLOCSP
Date: Tue, 16 Jun 2009 12:32:39 -0500	[thread overview]
Message-ID: <4A37D737.70004@sandeen.net> (raw)
In-Reply-To: <8770d98c0906161028j1cc5cbadl49d30092fddf3dbe@mail.gmail.com>

Smit Shah wrote:
> On 6/16/09, Felix Blyakher <felixb@sgi.com> wrote:
>> On Jun 16, 2009, at 10:16 AM, Eric Sandeen wrote:


>>> Maybe I should ask what the end goal is here.  :)
>>>
> Just to see if preallocation using fallocate helps reducing the
> fragmentation and increases the throughput.  I guess it wll help
> reduce the fragmentation but the write performance is going to suffer.

Depends on the IO you do, I think.  I'd be curious to know exactly how
you're running preallocation & iometer so I could give it a shot, to see
why xfs seems to be doing worse than ext4.

Thanks,
-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-06-16 17:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  0:18 XFS Preallocate using ALLOCSP Smit Shah
2009-06-16  2:00 ` Smit Shah
2009-06-16  3:34 ` Eric Sandeen
2009-06-16  6:44   ` Smit Shah
2009-06-16  7:34     ` Smit Shah
2009-06-16 15:16     ` Eric Sandeen
2009-06-16 16:42       ` Felix Blyakher
2009-06-16 17:28         ` Smit Shah
2009-06-16 17:32           ` Eric Sandeen [this message]
2009-06-16 21:38             ` Smit Shah
2009-06-17  1:04               ` Michael Monnerie
2009-06-16 17:41           ` Felix Blyakher
2009-06-16 21:42             ` Smit Shah
2009-06-16 22:05               ` Eric Sandeen
2009-06-16 22:32                 ` Felix Blyakher
2009-06-16 22:19               ` Smit Shah
2009-06-16 22:26               ` Felix Blyakher

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=4A37D737.70004@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=getsmit@gmail.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.