From: Dave Chinner <david@fromorbit.com>
To: Ewen McNeill <xfs@ewen.mcneill.gen.nz>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Rationale for hardware RAID 10 su, sw values in FAQ
Date: Thu, 21 Dec 2017 09:29:33 +1100 [thread overview]
Message-ID: <20171220222933.GH4094@dastard> (raw)
In-Reply-To: <0dbebe1a-4704-0880-87cc-f029921b6c7f@mcneill.gen.nz>
On Tue, Dec 19, 2017 at 03:19:32PM +1300, Ewen McNeill wrote:
> Hi Dave,
>
> On 28/09/17 12:36, Ewen McNeill wrote:
> >Perhaps the perfect is the enemy of the good here. Would it help
> >if I were to write up some text covering:
> >[... storage media/RAID considerations for xfs layout ...]
> >
> >(No promises when, but "October" seems plausible if this would be useful.)
>
> So... October proved not to be plausible. But I'm still considering
> writing something, perhaps while it's quieter over late
> December/early January.
>
> AFAICT the relevant "TODO" section of:
>
> https://git.kernel.org/pub/scm/fs/xfs/xfs-documentation.git/tree/admin/XFS_Performance_Tuning/filesystem_tunables.asciidoc
>
> is unchanged.
>
> If it's still useful to write something, I'll see if there's a quiet
> "home" day over the holidays to write a page or so about the
> considerations I'm aware of as a SysAdmin.
Sure, if you've got time to write something it would be greatly
appreciated.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2017-12-20 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 8:54 Rationale for hardware RAID 10 su, sw values in FAQ Ewen McNeill
2017-09-27 0:43 ` Dave Chinner
2017-09-27 1:56 ` Ewen McNeill
2017-09-27 4:33 ` Dave Chinner
2017-09-27 23:36 ` Ewen McNeill
2017-09-28 1:39 ` Dave Chinner
2017-09-28 10:53 ` Emmanuel Florac
2017-09-28 11:07 ` Dave Chinner
2017-12-19 2:19 ` Ewen McNeill
2017-12-20 22:29 ` Dave Chinner [this message]
2018-02-06 1:56 ` Storage considerations for XFS layout documentation (was Re: Rationale for hardware RAID 10 su, sw values in FAQ) Ewen McNeill
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=20171220222933.GH4094@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=xfs@ewen.mcneill.gen.nz \
/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.