Re: bsrange doesn't accept separate read,write values

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2011-07-23 20:53, Dave Engberg wrote:
> The 'bs' and 'bssplit' configuration variables accept separate numbers for read and write operations if you separate them with a comma. For example:
> bssplit=1k/39:8k/50:64k/11,1k/29:8k/50:64k/21
> 
> The documentation for 'bsrange' says it works the same way, but if I try to specify two ranges with a comma, I get an error when I run the app. E.g. if I put this line in the configuration file:
> bsrange=1k-16k,2k-32k
> 
> I get this error output:
> 
> fio: pid=26861, err=22/file:engines/sync.c:62, func=xfer, error=Invalid argument
> 
> Here's my attempt at a patch for this:
> 
> 
> *** fio-1.57-orig/parse.c    2011-07-14 11:20:25.000000000 -0700
> --- fio-1.57/parse.c    2011-07-23 11:38:12.000000000 -0700
> ***************
> *** 453,458 ****
> --- 453,464 ----
> 
>             strncpy(tmp, ptr, sizeof(tmp) - 1);
> 
> +         // Handle bsrange with separate read,write values:
> +         p1 = strchr(tmp, ',');
> +         if (p1) {
> +           *p1 = '\0';
> +         }
> +
>             p1 = strchr(tmp, '-');
>             if (!p1) {
>                 p1 = strchr(tmp, ':');
> 

Does this actually work, do you get the ranges set correctly? bssplit
has a separate parse handler for the range.

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux