From: Jens Axboe <axboe@kernel.dk>
To: Omar Sandoval <osandov@osandov.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [GIT PULL] New test and a fixup for blktests
Date: Mon, 26 Jun 2017 15:02:55 -0600 [thread overview]
Message-ID: <99056c08-07c3-5753-cea0-3e44affa435d@kernel.dk> (raw)
In-Reply-To: <20170626204539.GD6710@vader.dhcp.thefacebook.com>
On 06/26/2017 02:45 PM, Omar Sandoval wrote:
> On Wed, Jun 21, 2017 at 09:22:47AM -0600, Jens Axboe wrote:
>> Hi Omar,
>>
>> Two changes here:
>>
>> - block/006 wants to use the iops results, but it isn't using _fio_perf.
>> - Add block/010 to test for shared vs non-shared tags performance.
>>
>>
>> https://github.com/axboe/blktests.git axboe
>>
>>
>> ----------------------------------------------------------------
>> Jens Axboe (2):
>> block/006: use _fio_perf to get perf results
>> block/010: add test case for shared/unshared tags
>>
>> tests/block/006 | 4 +--
>> tests/block/010 | 82 +++++++++++++++++++++++++++++++++++++++++++++++++++++
>> tests/block/010.out | 2 ++
>> 3 files changed, 86 insertions(+), 2 deletions(-)
>> create mode 100755 tests/block/010
>> create mode 100644 tests/block/010.out
>>
>> --
>> Jens Axboe
>>
>
> Thanks, Jens, applied the first one, but
>
> [ 1876.142470] null_blk: unknown parameter 'shared_tags' ignored
>
> Am I missing a patch?
Yes, the shared tags is a new feature, it's coming in 4.13. But I checked
and it doesn't abort the module load. So the test ends up just being the
same thing run twice, if shared_tags isn't available. I figured that
was good enough.
--
Jens Axboe
next prev parent reply other threads:[~2017-06-26 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 15:22 [GIT PULL] New test and a fixup for blktests Jens Axboe
2017-06-26 20:45 ` Omar Sandoval
2017-06-26 21:02 ` Jens Axboe [this message]
2017-06-26 21:04 ` Omar Sandoval
2017-06-26 21:05 ` 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=99056c08-07c3-5753-cea0-3e44affa435d@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=osandov@osandov.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox