From: Marko Weber|8000 <weber@zbfmail.de>
To: Xfs <xfs@oss.sgi.com>
Subject: Re: gentoo linux, kernel 3.10.31 mount options bug?
Date: Tue, 25 Feb 2014 09:10:35 +0100 [thread overview]
Message-ID: <a9ad8075-ec2b-476e-bb51-40a93e879b1d@email.android.com> (raw)
In-Reply-To: <530A71E3.9060107@hardwarefreak.com>
[-- Attachment #1.1: Type: text/plain, Size: 1008 bytes --]
Thanks for the short and clear answer stan.
Marko
On 23. Februar 2014 23:10:43 MEZ, Stan Hoeppner <stan@hardwarefreak.com> wrote:
>On 2/23/2014 3:37 AM, Marko Weber|8000 wrote:
>...
>> linux /bzImage-3.10.31 root=/dev/md2 elevator=cfq clocksource=hpet
> ^^^^^^^^^^^^
>
>cfq tends to defeat much of the parallelism in XFS, decreasing
>throughput substantially. This is documented in the XFS FAQ and has
>been discussed here many times in the past. It has been recommended
>for
>a few years now that XFS not be used with the cfq elevator. Use
>deadline with md arrays on plain HBAs and noop on SSDs or any device
>with [F|B]BWC, i.e. RAID HBA or SAN controller.
>
>If you're using cfq to allow shaping of per process IO with control
>groups, simply using cfq alone may slow down XFS throughput to the
>point
>that you don't need to bother with control group optimizations.
>
>--
>Stan
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
[-- Attachment #1.2: Type: text/html, Size: 1449 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-02-25 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 9:37 gentoo linux, kernel 3.10.31 mount options bug? Marko Weber|8000
2014-02-23 16:07 ` Eric Sandeen
2014-02-23 22:10 ` Stan Hoeppner
2014-02-25 8:10 ` Marko Weber|8000 [this message]
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=a9ad8075-ec2b-476e-bb51-40a93e879b1d@email.android.com \
--to=weber@zbfmail.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