All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Schwartz <schwartz.xn@gmail.com>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: NCQ Priority Support and FIO
Date: Fri, 3 Feb 2017 17:03:17 -0700	[thread overview]
Message-ID: <CADAGN7UzGuCBbTs3URhqi6RiwNrOs-jLu0VtVRmT6nWvMnjPHg@mail.gmail.com> (raw)
In-Reply-To: <CALjAwxgQVhaviwg0wEqsqqHCsyksf0ES+E6-S3ON7HhUMn17ng@mail.gmail.com>

Thanks for the info, I'll play around with that option and see if I
can make that work.  Is there anything that would allow me to control
the amount of priority commands from within a single thread?

Regards,
Brandon

On Thu, Feb 2, 2017 at 3:36 PM, Sitsofe Wheeler <sitsofe@gmail.com> wrote:
> Hi,
>
> Perhaps you could use multiple threads and utilise the flow
> (http://fio.readthedocs.io/en/sphinx-doc/fio_doc.html#cmdoption-arg-flow
> ) control on pairs of threads?
>
> On 2 February 2017 at 22:29, Brandon Schwartz <schwartz.xn@gmail.com> wrote:
>>
>> 60% RandomRead / 40% RandomWrite but of those reads, have 15% be high priority
>>
>> Or is there a way to get this sort of priority testing done with
>> current FIO?
>
> --
> Sitsofe | http://sucs.org/~sits/

  reply	other threads:[~2017-02-04  0:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 22:29 NCQ Priority Support and FIO Brandon Schwartz
2017-02-02 22:36 ` Sitsofe Wheeler
2017-02-04  0:03   ` Brandon Schwartz [this message]
2017-02-04  7:37     ` Sitsofe Wheeler
2017-04-08  9:06       ` Sitsofe Wheeler
2017-09-05 18:45         ` Brandon Schwartz
2017-09-08  6:20           ` Sitsofe Wheeler

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=CADAGN7UzGuCBbTs3URhqi6RiwNrOs-jLu0VtVRmT6nWvMnjPHg@mail.gmail.com \
    --to=schwartz.xn@gmail.com \
    --cc=fio@vger.kernel.org \
    --cc=sitsofe@gmail.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 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.