All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/2] mkfs: default log size for small filesystems too large
Date: Fri, 28 Feb 2014 12:03:23 +1100	[thread overview]
Message-ID: <20140228010323.GG30131@dastard> (raw)
In-Reply-To: <530FBC2F.4070301@sandeen.net>

On Thu, Feb 27, 2014 at 04:29:03PM -0600, Eric Sandeen wrote:
> On 2/27/14, 3:45 AM, Dave Chinner wrote:
> > From: Dave Chinner <dchinner@redhat.com>
> > 
> > Recent changes to the log size scaling have resulted in using the
> > default size multiplier for the log size even on small filesystems.
> > Commit 88cd79b ("xfs: Add xfs_log_rlimit.c") changed the calculation
> > of the maximum transaction size that the kernel would issues and
> > that significantly increased the minimum size of the default log.
> > As such the size of the log on small filesystems was typically
> > larger than the prefious default, even though the previous default
> > was still larger than the minimum needed.
> > 
> > Rework the default log size calculation such that it will use the
> > original log size default if it is larger than the minimum log size
> > required, and only use a larger log if the configuration of the
> > filesystem requires it.
> > 
> > This is especially obvious in xfs/216, where the default log size is
> > 10MB all the way up to 16GB filesystems. The current mkfs selects a
> > log size of 50MB for the same size filesystems and this is
> > unnecessarily large.
> > 
> > Return the scaling of the log size for small filesystems to
> > something similar to what xfs/216 expects.
> 
> I can confirm that this fixes xfs/216, but I've lost the thread on
> why log size scaling was changed at all in 88cd79b, and why we now
> end up with something different in mkfs.xfs than what we originally
> had....  Are there resulting functional changes?  Cosmetic?  What's
> going on with log scaling, and who moved my cheese?  :)

tl;dr: I screwed up with the original change that caused the log
size to increase. It wasn't caught by review, it caused quite a few
problems for xfstests, and some of the things it was doing made no
sense. So this patch  is reverting the behaviour back to -almost-
the same as the 3.1.x series.

The only difference is that now the minimum log size takes into
account sunit padding on log writes IOWs, the log sizes should be
identical to 3.1.x for filesystems with lsu=0 and that's why tests
like xfs/216 pass again....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2014-02-28  1:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27  9:45 [PATCH 0/2] xfsprogs: mkfs fixes Dave Chinner
2014-02-27  9:45 ` [PATCH 1/2] mkfs: default log size for small filesystems too large Dave Chinner
2014-02-27 22:29   ` Eric Sandeen
2014-02-28  1:03     ` Dave Chinner [this message]
2014-02-28  3:12   ` Eric Sandeen
2014-02-28 13:09   ` Brian Foster
2014-02-27  9:45 ` [PATCH 2/2] mkfs: proto file creation does not set ftype correctly Dave Chinner
2014-02-27 14:17   ` Eric Sandeen
2014-02-27 19:40     ` Dave 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=20140228010323.GG30131@dastard \
    --to=david@fromorbit.com \
    --cc=sandeen@sandeen.net \
    --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 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.