public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Niv Sardi <xaiki@cxhome.ath.cx>
Cc: David Chinner <dgc@sgi.com>, Niv Sardi <xaiki@sgi.com>,
	sgi.bugs.xfs@fido.engr.sgi.com, xfs-dev@sgi.com, xfs@oss.sgi.com
Subject: Re: ADD 977766 - mkfs.xfs man page needs the default settings updated. [REVIEW TAKE 3]
Date: Tue, 11 Mar 2008 12:15:14 +1100	[thread overview]
Message-ID: <20080311011514.GE155407@sgi.com> (raw)
In-Reply-To: <416c461f0803092315m7ae6f55ek9b64058c3793aaa7@mail.gmail.com>

On Mon, Mar 10, 2008 at 05:15:04PM +1100, Niv Sardi wrote:
> On Mon, Mar 10, 2008 at 5:07 PM, David Chinner <dgc@sgi.com> wrote:
> >  Secondly, version one logs are not being kept around for backwards
> >  compatibility reasons. It's a valid, supported configuration, and in
> >  some cases performs better than version 2 logs....
> 
> Can you be more specific ?

More specific about which comment?

Re: performance - specSFS.

IIRC, anything that is effectively a synchronous transaction workload
tends to perform slightly better with v1 logs than v2 logs. It's
in the order of a few percent, but some ppl kill for that ;)

> the man page should document when this is
> better supported and I believe you're the one that has the best
> knowledge about that.
> 
> >  Realistically, I see no need for changing this text except to add that
> >  the default is version 2.
> 
> The change was motivated by Eric's comments on OSS that it is not
> clear why one should pick log v1 or v2, and I believe he is right.

If you don't understand - use the default. In most cases v2 logs are the
right thing to use and no amount of text in the man page is going to be
able to explain the corner cases where you'd want to use v1 logs....

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2008-03-11  1:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <incident_977766@bugworks.engr.sgi.com>
     [not found] ` <20080222003514.8D88E2C3@toolshop.engr.sgi.com>
     [not found]   ` <nccskzlzg9f.fsf_-_@sgi.com>
     [not found]     ` <nccablbf8ra.fsf_-_@sgi.com>
     [not found]       ` <20080310060751.GY155407@sgi.com>
2008-03-10  6:15         ` ADD 977766 - mkfs.xfs man page needs the default settings updated. [REVIEW TAKE 3] Niv Sardi
2008-03-11  1:15           ` David Chinner [this message]
2008-03-11  1:45             ` 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=20080311011514.GE155407@sgi.com \
    --to=dgc@sgi.com \
    --cc=sgi.bugs.xfs@fido.engr.sgi.com \
    --cc=xaiki@cxhome.ath.cx \
    --cc=xaiki@sgi.com \
    --cc=xfs-dev@sgi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox