From: keith.busch@intel.com (Keith Busch)
Subject: Hang when running LLVM+clang test suite
Date: Mon, 22 Jan 2018 11:37:42 -0700 [thread overview]
Message-ID: <20180122183742.GP12043@localhost.localdomain> (raw)
In-Reply-To: <26A085AA-98EB-4ACC-A0B2-0F30E7AAC33E@znu.io>
On Sun, Jan 21, 2018@09:13:27AM -0500, David Zarzycki wrote:
> To my surprise, I think I?ve narrowed down the bug to the block multi-queue layer. Can you please confirm that the following test is reasonable?
>
> 1) Create a file in /tmp (tmpfs with plenty of RAM and 2x the size needed by the test suite)
> 2) ?losetup? the file
> 3) 'cat /sys/block/loop0/queue/scheduler' ("[mq-deadline] none? in this case)
> 4) Create ext4 partition on /dev/loop0 and mount it
> 5) Run stress test in the loopback filesystem
The test looks fair to run. Does your error only happen if using
mq-deadline, or are there problems when using "none"?
next prev parent reply other threads:[~2018-01-22 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 10:47 Hang when running LLVM+clang test suite David Zarzycki
2018-01-21 2:50 ` Keith Busch
2018-01-21 13:49 ` David Zarzycki
2018-01-21 14:13 ` David Zarzycki
2018-01-22 18:37 ` Keith Busch [this message]
2018-01-22 23:33 ` David Zarzycki
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=20180122183742.GP12043@localhost.localdomain \
--to=keith.busch@intel.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