On 11/30/2017 04:47 PM, Jens Axboe wrote:
> On 11/30/2017 04:41 PM, Phillip Chen wrote:
>> It appears that there is a limitation of 64 maximum zones. I tried to
>> use 200 zones (100 empty and 100 with 1%) and I got the following
>> error: "fio: access percentage don't add up to 100 for zoned random
>> distribution (got=32)". Would it be possible to extend the number of
>> zones up to 256 (since 200 is the maximum that you'd be able to use
>> since the percentage is the smallest chance usable)?
>> Here's the string I was using:
>> fio --name=rand_reads --ioengine=libaio --direct=1 --exitall --thread
>> --filename=/dev/sde --runtime=30 --readwrite=randread --iodepth=1
>> --random_distribution=zoned_abs:0/1879048192:1/256m:0/44023414784:1/256m:0/2415919104:1/256m:0/4563402752:1/256m:0/2415919104:1/256m:0/116500987904:1/256m:0/18253611008:1/256m:0/107642617856:1/256m:0/82946555904:1/256m:0/34359738368:1/256m:0/53687091200:1/256m:0/98247376896:1/256m:0/74088185856:1/256m:0/28185722880:1/256m:0/28722593792:1/256m:0/2415919104:1/256m:0/27380416512:1/256m:0/116769423360:1/256m:0/27380416512:1/256m:0/24159191040:1/256m:0/3221225472:1/256m:0/33554432000:1/256m:0/63619203072:1/256m:0/13958643712:1/256m:0/37312528384:1/256m:0/8589934592:1/256m:0/53687091200:1/256m:0/36507222016:1/256m:0/48586817536:1/256m:0/3489660928:1/256m:0/86436216832:1/256m:0/70866960384:1/256m:0/163477192704:1/256m:0/96099893248:1/256m:0/17985175552:1/256m:0/22817013760:1/256m:0/30064771072:1/256m:0/15300820992:1/256m:0/61740154880:1/256m:0/16911433728:1/256m:0/64961380352:1/256m:0/21206401024:1/256m:0/30870077440:1/256m:0/49660559360:1/256m:0/47513075712:1/256m:0/6710886400:1/256m:0/5637144576:1/256m:0/1879048192:1/256m:0/71940702208:1/256m:0/34896609280:1/256m:0/25232932864:1/256m:0/42949672960:1/256m:0/12079595520:1/256m:0/58787364864:1/256m:0/11005853696:1/256m:0/31943819264:1/256m:0/15837691904:1/256m:0/76772540416:1/256m:0/24427626496:1/256m:0/16642998272:1/256m:0/4831838208:1/256m:0/17179869184:1/256m:0/34628173824:1/256m:0/70330089472:1/256m:0/20937965568:1/256m:0/21474836480:1/256m:0/22548578304:1/256m:0/8321499136:1/256m:0/87509958656:1/256m:0/33017561088:1/256m:0/2952790016:1/256m:0/2415919104:1/256m:0/42949672960:1/256m:0/79725330432:1/256m:0/48586817536:1/256m:0/4563402752:1/256m:0/5905580032:1/256m:0/20669530112:1/256m:0/17179869184:1/256m:0/4563402752:1/256m:0/121064390656:1/256m:0/41875931136:1/256m:0/63082332160:1/256m:0/13958643712:1/256m:0/17985175552:1/256m:0/46707769344:1/256m:0/1342177280:1/256m:0/23085449216:1/256m:0/38654705664:1/256m:0/47244640256:1/256m:0/5100273664:1/256m:0/77846282240:1/256m:0/17179869184:1/256m:0/18522046464:1/256m:0/40533753856:1/256m:0/83483426816:1/256m:0/1342177280
:1/256m:0/61471719424:1/256m:0/61740154880:1/256m:0/100126425088:1/256m
>> --output-format=terse
>
> That's correct, there's an imposed limit of 64 zones. The only issue with
> lifting that limit is that it severely bumps the size of the packed
> variant of the thread options. Going from 64 to 256 would make that
> about 9k larger. Just an on-wire thing, so not a huge concern.
If you git pull, it should support up to 256.
--
Jens Axboe
��.n��������+%������w��{.n�������^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
