All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Juan Simón" <decedion@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: recommended scheduler for HDD drives
Date: Sat, 8 Jan 2022 13:42:29 +0100	[thread overview]
Message-ID: <CAMQzBqCGTw8+Fg7ErAOeC7t_vjAhBVjUzk_eB9qTnAL_xzykOg@mail.gmail.com> (raw)

Hi,
I'm going to install a WD Ultrastar DC HC550 18 TB in a desktop PC
with Arch Linux and kernel 5.15.13. It will primarily store big HD
video files (1080p/4K) and it will be used for streaming.
In the FAQ the question on this topic
(https://xfs.org/index.php/XFS_FAQ#Q:_Which_I.2FO_scheduler_for_XFS.3F)
is not valid for recent versions of the Linux kernel:
--------------------------------------------------------------------------------------
.....
Q: Which I/O scheduler for XFS?
On rotational disks without hardware raid
CFQ: not great for XFS parallelism
....
deadline: good option, doesn't have such problem
Note that some kernels have block multiqueue enabled which (currently
- 08/2016) doesn't support I/O schedulers at all thus there is no
optimisation and reordering IO for best seek order, so disable blk-mq
for rotational disks (see CONFIG_SCSI_MQ_DEFAULT, CONFIG_DM_MQ_DEFAULT
options and use_blk_mq parameter for scsi-mod/dm-mod kernel modules).
....
--------------------------------------------------------------------------------------

Single-queue schedulers were removed from kernel since Linux 5.0.
Which would be the best MQ I/O Scheduler to use: mq-deadline, bfq or none?
Thanks in advance. Regards.

                 reply	other threads:[~2022-01-08 12:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAMQzBqCGTw8+Fg7ErAOeC7t_vjAhBVjUzk_eB9qTnAL_xzykOg@mail.gmail.com \
    --to=decedion@gmail.com \
    --cc=linux-xfs@vger.kernel.org \
    /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.