From: Jens Axboe <axboe@kernel.dk>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: cpus_allowed_policy for async IO verification threads
Date: Thu, 04 Sep 2014 13:56:23 -0600 [thread overview]
Message-ID: <5408C3E7.2050105@kernel.dk> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B402958C4F41B@G4W3202.americas.hpqcorp.net>
On 09/04/2014 01:40 PM, Elliott, Robert (Server Storage) wrote:
> To accompany cpus_allowed_policy=split, should fio offer
> a verify_async_cpus_allowed_policy=split to bind its
> async IO verification threads to particular CPUs?
>
> verify_async_cpus=str
> Tell fio to set the given CPU affinity on
> the async IO verification threads. See cpus_allowed for
> the format used.
That would probably not be a bad idea.
--
Jens Axboe
prev parent reply other threads:[~2014-09-04 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 19:40 cpus_allowed_policy for async IO verification threads Elliott, Robert (Server Storage)
2014-09-04 19:56 ` Jens Axboe [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=5408C3E7.2050105@kernel.dk \
--to=axboe@kernel.dk \
--cc=Elliott@hp.com \
--cc=fio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox