Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: [PATCH] Fix documentation of SI vs. binary prefixes
Date: Tue, 11 Feb 2014 09:39:36 -0700	[thread overview]
Message-ID: <20140211163936.GI19057@kernel.dk> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B4029548A6481@G9W0745.americas.hpqcorp.net>

On Tue, Feb 11 2014, Elliott, Robert (Server Storage) wrote:
> fio specifies SI and binary units backwards, presumably for
> compatibility with old scripts.  The description in HOWTO and the man
> page should acknowledge this.  I suggest fixing it something like
> this.

It's weird how that happened, I don't even remember, to be honest. I
would agree with John here that we just need to make the painful switch,
and potentially add a switch for backwards compatability.

-- 
Jens Axboe



      parent reply	other threads:[~2014-02-11 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11  0:40 [PATCH] Fix documentation of SI vs. binary prefixes Elliott, Robert (Server Storage)
2014-02-11  4:45 ` John Williams
2014-02-11 16:39 ` Jens Axboe [this message]

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=20140211163936.GI19057@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Elliott@hp.com \
    --cc=fio@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox