public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com
Subject: Re: raid10n2/xfs setup guidance on write-cache/barrier
Date: Fri, 23 Mar 2012 23:48:08 +0100	[thread overview]
Message-ID: <201203232348.09158.Martin@lichtvoll.de> (raw)
In-Reply-To: <20331.39194.377610.888636@tree.ty.sabi.co.UK>

Am Donnerstag, 22. März 2012 schrieb Peter Grandi:
> Overselling 'delaylog' with cheeky propaganda glossing over the
> heavy tradeoffs involved is understandable, but quite wrong.

Thing is, as far as I understand Dave´s slides and recent entries in 
Kernelnewbies Linux Changes as well as Heise Open Kernel log is that - 
beside delaylog - there has been quite some other metadata related 
performance improvements.

Thus IMHO reducing the recent improvements in metadata performance is 
underselling XFS and overselling delaylog. Unless of course all those 
recent performance improvements could not have been done without the 
delaylog mode.

That said, this is just my interpretation. If all recent improvements are 
only due to delaylog, then I am obviously off track.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

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

  parent reply	other threads:[~2012-03-23 22:48 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA8mOyDKrWg0QUEHxcD4ocXXD42nJu0TG+sXjC4j2RsigHTcmw@mail.gmail.com>
     [not found] ` <4F61803A.60009@hardwarefreak.com>
     [not found]   ` <CAA8mOyCzs36YD_QUMq25HQf8zuq1=tmSTPjYdoFJwy2Oq9sLmw@mail.gmail.com>
2012-03-15 14:07     ` raid10n2/xfs setup guidance on write-cache/barrier Peter Grandi
2012-03-15 15:25       ` keld
2012-03-15 16:52         ` Jessie Evangelista
2012-03-15 17:15           ` keld
2012-03-15 17:40             ` keld
2012-03-15 16:18       ` Jessie Evangelista
2012-03-15 23:00         ` Peter Grandi
2012-03-16  3:36           ` Jessie Evangelista
2012-03-16 11:06             ` Michael Monnerie
2012-03-16 12:21               ` Peter Grandi
2012-03-16 17:15             ` Brian Candler
2012-03-17 15:35             ` Peter Grandi
2012-03-17 21:39               ` raid10n2/xfs setup guidance on write-cache/barrier (GiB alignment) Zdenek Kaspar
2012-03-18  0:08                 ` Peter Grandi
2012-03-26 19:50               ` raid10n2/xfs setup guidance on write-cache/barrier Martin Steigerwald
2012-03-17  4:21       ` NOW:Peter goading Dave over delaylog - WAS: " Stan Hoeppner
2012-03-17 22:34         ` Dave Chinner
2012-03-18  2:09           ` Peter Grandi
2012-03-18 11:25             ` Peter Grandi
2012-03-18 14:00               ` Christoph Hellwig
2012-03-18 19:17                 ` Peter Grandi
2012-03-19  9:07                   ` Stan Hoeppner
2012-03-20 12:34                     ` Jessie Evangelista
2012-03-18 18:08               ` Stan Hoeppner
2012-03-22 21:26                 ` Peter Grandi
2012-03-23  5:10                   ` Stan Hoeppner
2012-03-23 22:48                   ` Martin Steigerwald [this message]
2012-03-24  1:27                     ` Peter Grandi
2012-03-24 16:27                       ` GNU 'tar', Schilling's 'tar', write-cache/barrier Peter Grandi
2012-03-24 17:11                         ` Brian Candler
2012-03-24 18:35                           ` Peter Grandi
     [not found]     ` <4F633121.10800@hardwarefreak.com>
     [not found]       ` <CAKuK5J3GHgWcnYLqwRV8s_wMjO2nBVf7h=yONtn90kPn9A_3Gg@mail.gmail.com>
     [not found]         ` <CAKuK5J11JTdwZSBWj7DH7c+hE--MVNQVVrcKXaV2AO-wEpWBog@mail.gmail.com>
2012-03-16 19:28           ` raid10n2/xfs setup guidance on write-cache/barrier Peter Grandi
2012-03-17  0:02             ` Stan Hoeppner

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=201203232348.09158.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --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