From: Jens Axboe <axboe@kernel.dk>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>,
"scameron@beardog.cce.hp.com" <scameron@beardog.cce.hp.com>
Subject: Re: [PATCH] fio: fix hangs due to iodepth_low
Date: Thu, 04 Sep 2014 13:55:49 -0600 [thread overview]
Message-ID: <5408C3C5.6010309@kernel.dk> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B402958C4F44A@G4W3202.americas.hpqcorp.net>
On 09/04/2014 01:42 PM, Elliott, Robert (Server Storage) wrote:
>
>
>> -----Original Message-----
>> From: Jens Axboe [mailto:axboe@kernel.dk]
>> Sent: Thursday, 04 September, 2014 9:39 AM
>> To: Elliott, Robert (Server Storage); fio@vger.kernel.org;
>> scameron@beardog.cce.hp.com
>> Subject: Re: [PATCH] fio: fix hangs due to iodepth_low
>>
>> On 09/04/2014 08:27 AM, Elliott, Robert (Server Storage) wrote:
>>>>> should be:
>>>>>
>>>>> if (min_events > td->cur_depth)
>>>>> min_events = td->cur_depth;
>>>>>
>>>>> and we should probably put this logic in io_u_queued_complete(),
>> I
>>>> think
>>>>> that would be a safer alternative instead of near the callers.
>>>
>>> io_u_quisce, which calls io_u_queued_complete with an argument
>>> of 1, includes this comment:
>>> * and cur_depth is meaningless for sync engines.
>>>
>>> If that is invoked during sync traffic too, then putting this
>>> change inside io_u_queued_complete might not work right.
>>
>> It's good enough for this use case. And it doesn't really matter if
>> it's
>> near the caller or in the function from this point of view, since
>> there
>> will be nothing (0) to complete for sync engines. By their very
>> nature,
>> they have nothing pending at that point. So I think the patch is fine
>> as
>> I sent out.
>
> I ran this version through similar tests and it works as well.
Great thanks Rob, I committed that fix.
--
Jens Axboe
next prev parent reply other threads:[~2014-09-04 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 0:23 [PATCH] fio: fix hangs due to iodepth_low Robert Elliott
2014-09-04 1:18 ` Stephen Cameron
2014-09-04 1:34 ` Jens Axboe
2014-09-04 1:36 ` Jens Axboe
2014-09-04 14:27 ` Elliott, Robert (Server Storage)
2014-09-04 14:38 ` Jens Axboe
2014-09-04 19:42 ` Elliott, Robert (Server Storage)
2014-09-04 19:55 ` Jens Axboe [this message]
2014-09-04 2:08 ` Elliott, Robert (Server Storage)
2014-09-04 2:11 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2014-09-04 0:23 Robert Elliott
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=5408C3C5.6010309@kernel.dk \
--to=axboe@kernel.dk \
--cc=Elliott@hp.com \
--cc=fio@vger.kernel.org \
--cc=scameron@beardog.cce.hp.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.