public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-block@vger.kernel.org, Omar Sandoval <osandov@fb.com>
Subject: Re: Kyber scheduler brings system to halt when used on swap partition
Date: Fri, 12 May 2017 12:30:00 -0700	[thread overview]
Message-ID: <20170512193000.GB15267@vader.DHCP.thefacebook.com> (raw)
In-Reply-To: <20170511125724.GA302@x4>

On Thu, May 11, 2017 at 02:57:24PM +0200, Markus Trippelsdorf wrote:
> Using the new Kyber mq scheduler brings my system to a halt as soon as it
> starts swapping. The swap partition resides on an SSD and is the only
> partition in use on that drive.
> Symptoms are stuttering sound and non moving mouse pointer. After a
> while the monitor switches off, because it gets no signal anymore.
> At which point only a hard reset will bring the system back.
> 
> "none" works fine.

Thanks for testing, I'm taking a look to see if there's anything special
about the swap path that would trigger this. In the meantime, if you
swapoff your swap partition and do some I/O on it, what happens? Here's
a first-order guess at a fio job you could run:

fio --group_reporting --filename=$partition \
	--name swapin --numjobs=8 --ioengine=sync --rw=randread \
	--name swapout --numjobs=4 --ioengine=libaio --iodepth=8 --rw=randwrite

Interesting to note is that wbt, which Kyber borrowed ideas from, treats
kswapd specially, allowing it to queue more I/O than other processes. I
wonder if we need to do the same in Kyber.

      reply	other threads:[~2017-05-12 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 12:57 Kyber scheduler brings system to halt when used on swap partition Markus Trippelsdorf
2017-05-12 19:30 ` Omar Sandoval [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=20170512193000.GB15267@vader.DHCP.thefacebook.com \
    --to=osandov@osandov.com \
    --cc=linux-block@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=osandov@fb.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