All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen Bates" <sbates@raithlin.com>
To: "Jens Axboe" <axboe@fb.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCHSET v3] block: IO polling improvements
Date: Wed, 16 Nov 2016 11:31:29 -0600	[thread overview]
Message-ID: <e25d7e34cde7a478b1593555bc980236.squirrel@webmail.raithlin.com> (raw)
In-Reply-To: <1478927487-12998-1-git-send-email-axboe@fb.com>

On Fri, November 11, 2016 11:11 pm, Jens Axboe wrote:
> Respun on top of for-4.10/block, dropping patches that have been
> merged. This patchset adds Christoph's simplified sync O_DIRECT bdev access
> mode, and implements a more efficient IO polling on top of it. For more
> details, see the v2 posting here:
>
> http://www.mail-archive.com/linux-block@vger.kernel.org/msg02079.html
>
>
> Changes since v2:
>
>
> - Adapt to blk stat changes
> - Make it explicit that only blk-mq supports polling
> - Fix a bug in the hrtimer code, switching to absolute mode if we
> have to loop around (thanks Omar).
>

Hi Jens

I applied this series cleanly on top of 2868f13c303e147 in your
for-4.10/block branch. I tested using a simple fio wrapper script [1] on a
low-latency NVMe SSD [2]. Here are some results:

io_poll  io_poll_delay  threads  latency  CPU/threads

0        N/A            1        17.0     47%
1        -1             1        13.8     100%
1        0              1        14.6     73%
1        10             1        17.0     56%

0        N/A            8        18.7     47%
1        -1             8        14.4     100%
1        0              8        15.7     73%
1        10             8        19.0     56%

The io_poll_delay option 0 is definitely a nice compromise between no
polling and 100% polling. The result for io_poll_delay=10us is interesting
as it implies there might be some mismatch between that value and the
completion time. However I think that is something we can improve on over
time and I don't see it as a reason to not get this series upstream.

For the series:

Tested-By: Stephen Bates <sbates@raithlin.com>
Reviewed-By: Stephen Bates <sbates@raithlin.com>

Cheers

Stephen

[1] https://github.com/sbates130272/fio-stuff/blob/master/misc/iopoll-test.sh
[2]
http://www.microsemi.com/products/storage/flashtec-nvram-drives/flashtec-nvram-drives

  parent reply	other threads:[~2016-11-16 17:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-12  5:11 [PATCHSET v3] block: IO polling improvements Jens Axboe
2016-11-12  5:11 ` [PATCH 1/3] block: fast-path for small and simple direct I/O requests Jens Axboe
2016-11-14 19:33   ` Omar Sandoval
2016-11-14 20:00     ` Jens Axboe
2016-11-14 20:00       ` Jens Axboe
2016-11-15 13:49       ` Christoph Hellwig
2016-11-12  5:11 ` [PATCH 2/3] blk-mq: implement hybrid poll mode for sync O_DIRECT Jens Axboe
2016-11-12  5:11 ` [PATCH 3/3] blk-mq: make the polling code adaptive Jens Axboe
2016-11-14 19:43   ` Omar Sandoval
2016-11-14 19:58     ` Jens Axboe
2016-11-14 19:58       ` Jens Axboe
2016-11-16 17:31 ` Stephen Bates [this message]
2016-11-16 20:59   ` [PATCHSET v3] block: IO polling improvements Jens Axboe
2016-11-16 20:59     ` Jens Axboe

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=e25d7e34cde7a478b1593555bc980236.squirrel@webmail.raithlin.com \
    --to=sbates@raithlin.com \
    --cc=axboe@fb.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@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 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.