From: Jens Axboe <axboe@kernel.dk>
To: flash yan <flashyan83@gmail.com>
Cc: Jeff Furlong <jeff.furlong@hgst.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Linux OS killed fio process because fio invoked oom_killer
Date: Fri, 25 Mar 2016 09:10:02 -0600 [thread overview]
Message-ID: <56F554CA.7080205@kernel.dk> (raw)
In-Reply-To: <CADvrUP8WUwWUJYOr_8zdkgM3+k-JAm9oMVseHCs1DEW9z7x9QA@mail.gmail.com>
On 03/25/2016 09:03 AM, flash yan wrote:
> I have tried your patch. It fixed the issue. But I don't understand
> "So we just kept piling on buffers to verify, but we never did".
> You mean that fio didn't run any verify job with verify_async enabled?
Right, it did not for your case. But that's because of the super short
loop and the time_based setup, otherwise it would have. That was
apparent while it was running too (not reads or V status), and in the
final output (no reads there either). So it was a corner case where
verify did not happen, since the referenced commit that broke it for
that case.
--
Jens Axboe
next prev parent reply other threads:[~2016-03-25 15:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 14:06 Linux OS killed fio process because fio invoked oom_killer flash yan
2016-03-22 16:30 ` Jens Axboe
2016-03-22 23:12 ` flash yan
2016-03-23 0:42 ` Jens Axboe
2016-03-23 15:10 ` flash yan
2016-03-23 19:29 ` Jeff Furlong
2016-03-23 22:51 ` flash yan
2016-03-23 23:32 ` Jeff Furlong
2016-03-24 12:50 ` flash yan
2016-03-24 14:06 ` Jens Axboe
2016-03-24 19:39 ` Jens Axboe
2016-03-24 23:33 ` flash yan
2016-03-25 15:03 ` flash yan
2016-03-25 15:10 ` Jens Axboe [this message]
2016-03-27 12:00 ` flash yan
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=56F554CA.7080205@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=flashyan83@gmail.com \
--cc=jeff.furlong@hgst.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.