Hello Robert. Elliott, Robert (Persistent Memory) - 24.10.17, 16:23: > > > I got this bug report for fio Debian package: > > > > > > > > > > > > fio: uses the opposite symbol for kibibytes/kilobytes (Kb/KiB) than Sorry for safelink crap. (Need to remember to use my own SMTP to circumvent it.) > https://bugs.debian.org/872321 > > > > Its right. Completely right. The current behavior of fio is broken. > > > > > > > > > > > > But if I choose to divert from upstream default, I break *all included > > > examples* unless I patch them up to and I risk bug reports "my script > > > broke cause you decided to divert from upstream default behavior". > > > No scripts were harmed in the process; the default still presumes that > scripts are specifying numbers based on binary units. You must add > kb_base=1000 to switch to correct units. I don´t really understand this one. If I would change fio´s default behavior, I bet scripts may break. I wouldn´t change the meaning of "k" anyway, but just of "kib" and "kb", but still if a script uses one of these, it would break. Additionally I would need to patch fio source code as I am not aware of any other way to change this default behavior. I decided that I won´t do that. So unless any change in upstream I will do with the README approach. However, likely after an initial fio 3.1 Debian package uploaded is done. I just asked my sponsor Sven Hoexter to review the package. > The user-readable text output changed to use correct units, but the > structured output formats intended for automated parsing did not change. Hmm, interesting. Thanks, Martin -- 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
