From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
ksummit-discuss@lists.linux-foundation.org,
Greg KH <gregkh@linuxfoundation.org>, Jens Axboe <axboe@fb.com>,
hare@suse.de, Tejun Heo <tj@kernel.org>,
osandov@osandov.com, Christoph Hellwig <hch@lst.de>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Addressing long-standing high-latency problems related to I/O
Date: Fri, 16 Sep 2016 13:53:39 +0200 [thread overview]
Message-ID: <1d22aa72-79f8-4640-5dda-1c14a6cb7da0@sandisk.com> (raw)
In-Reply-To: <CACRpkdb5+mw5CafFLWKr4vwcTVpO6FWUSiDifDOZ+oXAu_h7+A@mail.gmail.com>
On 09/16/2016 01:24 PM, Linus Walleij wrote:
> What do you guys at SanDisk use?
Hello Linus,
We use fio for block device performance measurements. Before we run fio
we disable C-state and P-state transitions to make sure that the results
will not depend on any frequency scaling algorithm. Furthermore, we
install a udev rule that sets the following block layer parameters for
non-rotational devices: add_random=0 and rq_affinity=2.
Bart.
next prev parent reply other threads:[~2016-09-16 11:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 7:55 Paolo Valente
2016-09-16 8:24 ` Greg KH
2016-09-16 8:59 ` Linus Walleij
2016-09-16 9:10 ` Bart Van Assche
2016-09-16 11:24 ` Linus Walleij
2016-09-16 11:46 ` Arnd Bergmann
2016-09-16 13:10 ` Paolo Valente
2016-09-16 13:36 ` Linus Walleij
2016-09-16 11:53 ` Bart Van Assche [this message]
2016-09-22 9:18 ` Ulf Hansson
2016-09-22 11:06 ` Linus Walleij
2016-09-16 15:15 ` James Bottomley
2016-09-16 18:48 ` Paolo Valente
2016-09-16 19:36 ` James Bottomley
2016-09-16 20:13 ` Paolo Valente
2016-09-19 8:17 ` Jan Kara
2016-09-17 10:31 ` Linus Walleij
2016-09-21 13:51 ` Grant Likely
2016-09-21 14:30 ` Bart Van Assche
2016-09-21 14:37 ` Paolo Valente
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=1d22aa72-79f8-4640-5dda-1c14a6cb7da0@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=axboe@fb.com \
--cc=b.zolnierkie@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=ksummit-discuss@lists.linux-foundation.org \
--cc=linus.walleij@linaro.org \
--cc=osandov@osandov.com \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox