From: Jens Axboe <axboe@kernel.dk>
To: Jeff Furlong <jeff.furlong@wdc.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio max blocksize
Date: Fri, 13 Jul 2018 21:05:33 -0600 [thread overview]
Message-ID: <a1f8111f-5b0f-1f6f-cab8-c02a35e35d3a@kernel.dk> (raw)
In-Reply-To: <MWHPR04MB0320FC699861B6963D67D54F8F580@MWHPR04MB0320.namprd04.prod.outlook.com>
On 7/13/18 5:59 PM, Jeff Furlong wrote:
> I fixed the buflen issue (just keep peeling the onion back and
> updating all associated vars), fixed bsrange, fixed "auto" tabs, and
> did some simple tests:
> # fio --name=test --ioengine=libaio --direct=1 --rw=trim --iodepth=1 --bs=4g --filename=/dev/nvme1n1 --number_ios=1
> # fio --name=test --ioengine=libaio --direct=1 --rw=trim --iodepth=1 --bs=1t --filename=/dev/nvme1n1 --number_ios=1
> # fio --name=test --ioengine=libaio --direct=1 --rw=trim --iodepth=1 --bsrange=4g-8g --filename=/dev/nvme1n1 --number_ios=2
>
> The open issue I have is parsing bssplit. I plumbed out bssplit.bs as
> a 64 bit value, but using the existing value_pair helpers (32 bit)
> seem to conflict. Don’t really want to duplicate chunks of code, so
> open to ideas there.
I'd just convert those helpers to deal with unsigned long long always,
that should work fine for the uint case.
Just a note that I'll be out all of next week, so you'll have plenty of
time to make this perfect before I get back :-)
--
Jens Axboe
next prev parent reply other threads:[~2018-07-14 3:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 21:15 fio max blocksize Jeff Furlong
2018-07-07 4:43 ` Sitsofe Wheeler
2018-07-12 17:15 ` Jens Axboe
2018-07-12 18:08 ` Jeff Furlong
2018-07-12 18:20 ` Jens Axboe
2018-07-12 19:11 ` Jeff Furlong
2018-07-12 19:38 ` Jens Axboe
2018-07-12 22:13 ` Jeff Furlong
2018-07-12 22:33 ` Jens Axboe
2018-07-12 22:47 ` Jeff Furlong
2018-07-12 22:49 ` Jens Axboe
2018-07-13 0:07 ` Elliott, Robert (Persistent Memory)
2018-07-13 17:46 ` Jeff Furlong
2018-07-13 23:59 ` Jeff Furlong
2018-07-14 3:05 ` Jens Axboe [this message]
2018-07-17 21:38 ` Jeff Furlong
2018-07-23 15:17 ` Jens Axboe
2018-07-23 16:33 ` Jeff Furlong
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=a1f8111f-5b0f-1f6f-cab8-c02a35e35d3a@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=jeff.furlong@wdc.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.