All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Abutalib Aghayev <agayev@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH] Log offsets of I/O operations
Date: Mon, 30 Jun 2014 21:00:15 -0600	[thread overview]
Message-ID: <53B2243F.4080901@kernel.dk> (raw)
In-Reply-To: <53B1E257.5070405@kernel.dk>

On 2014-06-30 16:19, Jens Axboe wrote:
> On 2014-06-30 16:09, Abutalib Aghayev wrote:
>>
>> On Mon, Jun 30 2014 at 17:50 PM, Jens Axboe <axboe@kernel.dk> wrote:
>>> On 2014-06-29 11:43, Abutalib Aghayev wrote:
>>>>
>>>> This is a quick and dirty patch to log offsets of I/O operations as
>>>> well.  It is useful if you would like to make offset vs latency plot
>>>> for
>>>> random I/O, which may not be interesting to many people, so feel
>>>> free to
>>>> ignore it.
>>>
>>> I can definitely see this being useful. But adding 8 bytes to every log
>>> entry complicates things, as fio is already memory intensive there when
>>> logging longer runs.
>>>
>>> I'd suggest having two logging types:
>>>
>>> struct io_sample {
>>>             uint64_t time;
>>>             uint64_t val;
>>>             uint32_t ddir;
>>>             uint32_t bs;
>>>             uint64_t offset;
>>
>> I assume you didn't mean offset being here as well.
>
> Ah no, of course not.
>
>>> struct io_sample_offset {
>>>             struct io_sample s;
>>>             uint64_t offset;
>>> };
>>>
>>> and using the right type for what you are logging. This means you'd need
>>> an option to switch on the offset logging, and that you'd need to store
>>> this in the iolog struct (whether to log offset or not) and use the
>>> appropriate size for allocating and extending the log entries when
>>> needed.
>>>
>>> Make sense?
>>
>> Yes, let me rework the patch.
>
> Thanks! Note that you also need to handle the client/server part.
> Half-assed attempt attached, not tested at all. Still needs the client
> part update.

I finished off the client bit and committed it, it was just a few lines 
of change and it was done. Also added documentation, etc. So current 
-git should be complete.

-- 
Jens Axboe



  reply	other threads:[~2014-07-01  3:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 17:43 [PATCH] Log offsets of I/O operations Abutalib Aghayev
2014-06-30 21:50 ` Jens Axboe
2014-06-30 22:09   ` Abutalib Aghayev
2014-06-30 22:19     ` Jens Axboe
2014-07-01  3:00       ` Jens Axboe [this message]
2014-07-01  7:51         ` Abutalib Aghayev

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=53B2243F.4080901@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=agayev@gmail.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.