From: Jens Axboe <axboe@kernel.dk>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH] backend: Add configurable non fatal error list
Date: Sun, 23 Sep 2012 20:32:19 +0200 [thread overview]
Message-ID: <505F55B3.5030008@kernel.dk> (raw)
In-Reply-To: <1348400769-12760-1-git-send-email-dmonakhov@openvz.org>
On 2012-09-23 13:46, Dmitry Monakhov wrote:
> Sometimes it is reasonable to perform test nearly system limits where
> errors are possible and expected, in that case one may provide non
> fatal error list which will be ignored during execution.
> This patch add two options:
> ignore_error: List of non fatal error
> error_dump: Whenever ignored list should be dumped to log.
This looks pretty good. I particularly like that you allow for both
numeric and error "name". It might be a good idea to make that non case
sensitive, though. Minor detail.
I have applied it, thanks!
--
Jens Axboe
prev parent reply other threads:[~2012-09-23 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 11:46 [PATCH] backend: Add configurable non fatal error list Dmitry Monakhov
2012-09-23 18:32 ` 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=505F55B3.5030008@kernel.dk \
--to=axboe@kernel.dk \
--cc=dmonakhov@openvz.org \
--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