All of lore.kernel.org
 help / color / mirror / Atom feed
From: Federico Sevilla III <jijo@fs3.ph>
To: xfs@oss.sgi.com
Subject: Re: ZFS, XFS, and EXT4 compared
Date: Sat, 01 Sep 2007 23:07:23 +0800	[thread overview]
Message-ID: <1188659243.4430.8.camel@auctoritas.fs3.ph> (raw)
In-Reply-To: <1188513751.24970.109.camel@edge.yarra.acx>

[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]

On Fri, 2007-08-31 at 08:42 +1000, Nathan Scott wrote:
> Possibly.  Far more importantly for XFS, there really needs to be some
> way for RAID drivers to say "even though I support write barriers, its
> not a good idea for filesystems to enable write barriers by default on
> me".  Enabling write barriers everywhere, by default, seems to have a
> far worse impact than any mkfs/mount option tweaking.

On all my systems with software RAID or dm-crypt (or both), mounting XFS
gives me a message about barriers being disabled because the underlying
device doesn't support it. For good measure I disable write caching on
all my systems with either software RAID or dm-crypt (or both).

Am I reading the thread correctly that even with this message showing
up, I still need to mount with nobarrier explicitly to improve
performance?

I also think it would be nice to add something like a modern-day tuning
FAQ for XFS. I know there's a bit on the FAQ already but perhaps it
needs an update?

Thanks.

-- 
Federico Sevilla III
F S 3 Consulting Inc.
http://www.fs3.ph

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-09-02 14:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30  6:16 ZFS, XFS, and EXT4 compared Jeffrey W. Baker
2007-08-30  6:25 ` Cyril Plisko
2007-08-30  6:25   ` [zfs-discuss] " Cyril Plisko
2007-08-30  6:27 ` mike
2007-08-30  7:07 ` Nathan Scott
2007-08-30 13:20   ` Christoph Hellwig
2007-08-30 18:57     ` Eric Sandeen
2007-08-30 19:09       ` Jeffrey W. Baker
2007-08-30 19:09         ` Jeffrey W. Baker
2007-08-30 19:14         ` Eric Sandeen
2007-08-30 22:42     ` Nathan Scott
2007-09-01 15:07       ` Federico Sevilla III [this message]
2007-09-02 23:00         ` Nathan Scott
2007-08-30 13:37 ` Jose R. Santos
2007-08-30 18:52   ` Jeffrey W. Baker
2007-08-30 19:53     ` Jose R. Santos
2007-08-30 18:33 ` Jim Mauro
2007-08-30 18:33   ` [zfs-discuss] " Jim Mauro
2007-08-30 19:07 ` eric kustarz
2007-08-30 19:07   ` [zfs-discuss] " eric kustarz

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=1188659243.4430.8.camel@auctoritas.fs3.ph \
    --to=jijo@fs3.ph \
    --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.