From: Jens Axboe <axboe@kernel.dk>
To: Brian Fulton <bfulton@google.com>
Cc: Akash Verma <akashv@google.com>, fio <fio@vger.kernel.org>
Subject: Re: [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based
Date: Mon, 04 May 2015 18:37:53 -0600 [thread overview]
Message-ID: <554810E1.2020301@kernel.dk> (raw)
In-Reply-To: <CANff2=NEJF6YJ-yzf5BcFjpLp_P83S3mRvk3baZdRj02mgqkMQ@mail.gmail.com>
On 05/04/2015 05:17 PM, Brian Fulton wrote:
> Hi Jens,
>
> Akash and I both discovered this bug and work together. He is
> currently on holiday for the next two weeks or so. I am currently
> using the same tests that originally discovered the bug to verify it
> is fixed.
Ah perfect, I didn't realize that!
> Out of curiosity, why is the comma required after the zero in order to
> initialize all elements to zero? I used this initializer instead of
> memset just as it was used here:
> https://github.com/axboe/fio/blob/master/cgroup.c#L26. Are there
> certain compilers that require the comma? I also checked the C99 spec
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf, Section
> 6.7.8, page 125, sections 1 and 21. I just want to make sure I'm not
> loosing my mind.
Actually I might be mistaken, it's just an array. For structs you need
the comma to ensure it zero fills the rest of the members, for arrays I
believe your approach was actually fine.
--
Jens Axboe
next prev parent reply other threads:[~2015-05-05 0:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 22:50 [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based Akash Verma
2015-05-04 20:42 ` Jens Axboe
2015-05-04 21:25 ` Brian Fulton
2015-05-04 22:02 ` Jens Axboe
2015-05-04 22:08 ` Jens Axboe
2015-05-04 23:17 ` Brian Fulton
2015-05-05 0:37 ` Jens Axboe [this message]
2015-05-05 1:12 ` Brian Fulton
2015-05-15 17:32 ` Brian Fulton
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=554810E1.2020301@kernel.dk \
--to=axboe@kernel.dk \
--cc=akashv@google.com \
--cc=bfulton@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.