All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Karl Cronburg <kcronbur@redhat.com>
Cc: fio@vger.kernel.org
Subject: Re: what is the sample logger doing when the buffer fills up?
Date: Thu, 7 Jul 2016 12:36:10 -0600	[thread overview]
Message-ID: <20160707183605.GB8567@kernel.dk> (raw)
In-Reply-To: <CAJ9yE1DPWmV0Hx_AAS5cKZR5qSFeqmqJVg7dgikQK=ZBje-e3A@mail.gmail.com>

On Wed, Jul 06 2016, Karl Cronburg wrote:
> Hello all,
> 
> When I change add_clat_sample() in stat.c to call add_log_sample() seven times
> instead of once, and I set DEF_LOG_ENTRIES=4096, I get the following in the clat
> log file (note first column is line number in the file):
> 
>   4089 143, 9832, 0, 131072
>   4090 143, 9832, 0, 131072
>   4091 143, 9832, 0, 131072
>   4092 143, 9832, 0, 131072
>   4093 143, 9832, 0, 131072
>   4094 143, 9832, 0, 131072
>   4095 143, 9832, 0, 131072
>   4096 143, 9834, 0, 131072
>   4097 170, 15982, 0, 131072
>   4098 170, 15982, 0, 131072
>   4099 170, 15982, 0, 131072
>   4100 170, 15982, 0, 131072
>   4101 170, 15982, 0, 131072
>   4102 170, 15982, 0, 131072
>   4103 170, 15982, 0, 131072
>   4104 170, 15985, 0, 131072
>   4105 170, 15985, 0, 131072
> 
> Notice the lonely '9834' value in the center, which should have 7
> exact copies of itself
> but gets cut off right at the buffer size of 4096 entries.
> 
> So if I'm interpreting this correctly, samples get silently dropped
> (or not properly printed?)
> when the buffer fills up. Is this a bug? Am I misinterpreting what the
> doubly linked list is
> for? I was under the impression that a new sample buffer should be
> added to the linked
> list when the current one fills up.

Fair to assume this is what your patch fixed, correct? Just wanted to
ensure that it's already fixed.

-- 
Jens Axboe



  reply	other threads:[~2016-07-07 18:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06 15:56 what is the sample logger doing when the buffer fills up? Karl Cronburg
2016-07-07 18:36 ` Jens Axboe [this message]
2016-07-07 19:46   ` Karl Cronburg
2016-07-07 21:04     ` Jeff Furlong
2016-07-07 21:44       ` Jens Axboe
2016-07-07 21:47         ` Jeff Furlong
2016-07-07 21:50           ` Jens Axboe
2016-07-18 18:24             ` Matthew Eaton
2016-07-19  0:09               ` Jeff Furlong
2016-07-20 20:29                 ` Karl Cronburg
2016-07-20 21:23                   ` Jeff Furlong
2016-07-20 21:28                     ` Jeff Furlong
2016-07-20 23:46                       ` Jens Axboe
2016-07-21 15:49                         ` Karl Cronburg
2016-07-21 17:00                           ` Jeff Furlong
2016-07-21 21:26                             ` Karl Cronburg
2016-07-21 23:26                               ` Jeff Furlong
2016-07-22 14:47                                 ` Jens Axboe
2016-07-22 15:55                                   ` Jens Axboe
2016-07-22 18:37                                     ` Jens Axboe
2016-07-22 18:52                                       ` Jeff Furlong
2016-07-22 18:55                                         ` Jens Axboe
2016-07-22 19:20                                           ` Jens Axboe
2016-07-22 19:40                                             ` Jeff Furlong
2016-07-22 19:49                                               ` Jens Axboe

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=20160707183605.GB8567@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=kcronbur@redhat.com \
    /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.