All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Ales Novak <alnovak@suse.cz>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: fix in the setting of logbsize
Date: Sun, 7 Jun 2015 08:32:00 +1000	[thread overview]
Message-ID: <20150606223200.GZ24666@dastard> (raw)
In-Reply-To: <55722AD9.2080105@sandeen.net>

On Fri, Jun 05, 2015 at 06:03:53PM -0500, Eric Sandeen wrote:
> On 6/5/15 5:22 PM, Dave Chinner wrote:
> 
> > On Fri, Jun 05, 2015 at 03:28:45PM +0200, Ales Novak wrote:
> >> However, this rule is only mentioned in the documentation, while it
> >> could be checked during the mount.
> > 
> > Where in the documentation is that mentioned?
> 
> Documentation/filesystems/xfs.txt:
> 
>   logbsize=value
>         Set the size of each in-memory log buffer.  The size may be
>         specified in bytes, or in kilobytes with a "k" suffix.
>         Valid sizes for version 1 and version 2 logs are 16384 (16k)
>         and 32768 (32k).  Valid sizes for version 2 logs also
>         include 65536 (64k), 131072 (128k) and 262144 (256k). The
>         logbsize must be an integer multiple of the log
>         stripe unit configured at mkfs time.

Ah, ok. I'll need to look at the history of that, because I think I
can see what it is intended to mean, but the "power-of-two" sizes
that are enforced will also enforce the "integer multiple" part,
too. I think it was more intended for people using wierd stripe
units (e.g. 96k) to say the equivalent on 2x96k is a valid log
buffer size. I suspect we need to revisit both the code and the
documentation here....

Cheers,

Dave.

-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2015-06-06 22:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 13:28 [PATCH] xfs: fix in the setting of logbsize Ales Novak
2015-06-05 13:28 ` Ales Novak
2015-06-05 22:22 ` Dave Chinner
2015-06-05 23:03   ` Eric Sandeen
2015-06-06 22:32     ` Dave Chinner [this message]
2015-07-03 15:09       ` Ales Novak
2015-06-07  9:16   ` Ales Novak
2015-06-08 13:04     ` Mark Tinguely
2015-06-25 22:58       ` Ales Novak

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=20150606223200.GZ24666@dastard \
    --to=david@fromorbit.com \
    --cc=alnovak@suse.cz \
    --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.