All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>,
	Alex Tomas <bzzz.tomas@gmail.com>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: delalloc fragmenting files?
Date: Wed, 07 Nov 2007 14:53:09 -0600	[thread overview]
Message-ID: <473225B5.2020103@redhat.com> (raw)
In-Reply-To: <20071107203716.GI3966@webber.adilger.int>

Andreas Dilger wrote:
> On Nov 06, 2007  13:54 -0600, Eric Sandeen wrote:
>> Hmm bad news is when I add uninit_groups into the mix, it goes a little
>> south again, with some out-of-order extents.  Not the end of the world,
>> but a little unexpected?

> I think part of the issue is that by default the groups marked BLOCK_UNINIT
> are skipped, to avoid dirtying those groups if they have never been used
> before.  This policy could be changed in the mballoc code pretty easily if
> you think it is a net loss.  Note that the size of the extents is large
> enough (120MB or more) that some small reordering is probably not going
> to affect the performance in any meaningful way.

You're probably right; on the other hand, this is about the simplest
test an allocator could wish for - a single-threaded large linear write
in big IO chunks.

In this case it's probably not a big deal; I do wonder how it might
affect the bigger picture though, with more writing threads, aged
filesystems, and the like.  Just thought it was worth pointing out, as I
started looking at allocator behavior in the simple/isolated/unrealistic
:) cases.

-Eric

  reply	other threads:[~2007-11-07 20:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 21:24 delalloc fragmenting files? Eric Sandeen
2007-10-26 22:19 ` Andreas Dilger
2007-10-27  2:54   ` Eric Sandeen
2007-10-27  3:08     ` Eric Sandeen
2007-10-31 21:01   ` Eric Sandeen
2007-11-01  0:35     ` Alex Tomas
2007-11-01 15:20       ` Eric Sandeen
2007-11-01 19:05         ` Eric Sandeen
2007-11-02  8:56           ` Alex Tomas
2007-11-02 15:41             ` Eric Sandeen
2007-11-04 18:36               ` Alex Tomas
2007-11-05 17:37                 ` Eric Sandeen
2007-11-05 17:39                   ` Eric Sandeen
2007-11-05 17:45                   ` Alex Tomas
2007-11-05 18:51                   ` Andreas Dilger
2007-11-05 18:54                     ` Eric Sandeen
2007-11-06 19:54                   ` Eric Sandeen
2007-11-07 20:37                     ` Andreas Dilger
2007-11-07 20:53                       ` Eric Sandeen [this message]
2007-10-29 19:13 ` Eric Sandeen

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=473225B5.2020103@redhat.com \
    --to=sandeen@redhat.com \
    --cc=bzzz.tomas@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    /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.