ikegami-t

Hi, > I don't know we can accept this as-is - it's bound to break people depending on the previous behaviour who aren't checking the headings... Also wouldn't the documentation...

Just fixed the commit message error as s/leves/levels/.

> I think this is dramatic enough that `FIO_SERVER_VER` will need ramping (see https://github.com/axboe/fio/blob/master/server.h#L51 ). I'm also unsure if all the tools that scoop up latency ranges will need re-testing:...

> @ikegami-t Will this impact the terse output https://fio.readthedocs.io/en/latest/fio_man.html#terse-output ? Yes the terse output will be increased the number of microsecond and millisecond latency outputs since those depth levels increased.

> Hmm that's going to be a problem because the column headings are no longer going to match and CSV is not self describing... Okay now I am thinking to...

> > Hmm that's going to be a problem because the column headings are no longer going to match and CSV is not self describing... > > Okay now I...

> @ikegami-t can you squash all these into one commit? Yes just squashed the changes as mentioned. Thank you.

> Hi @ikegami-t > > > > Give me a chance to investigate this. You are welcome to make a PR but don't include the following: > > > >...

> Okay, so Ubuntu is the distro. Can you confirm if it is 22.04? Yes I think so. > > > > In the mean time, I will go ahead...

> >> Okay, so Ubuntu is the distro. Can you confirm if it is 22.04? > > > > > Yes I think so. > > > > Can I...