public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andi Kleen <ak@linux.intel.com>,
	Corey Ashford <cjashfor@linux.vnet.ibm.com>,
	David Ahern <dsahern@gmail.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Matt Fleming <matt.fleming@intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf tools: Do not fail on processing out of order event
Date: Thu, 27 Nov 2014 12:16:26 -0200	[thread overview]
Message-ID: <20141127141626.GK3808@redhat.com> (raw)
In-Reply-To: <20141127140707.GB25752@krava.brq.redhat.com>

Em Thu, Nov 27, 2014 at 03:07:07PM +0100, Jiri Olsa escreveu:
> On Thu, Nov 27, 2014 at 11:53:00AM -0200, Arnaldo Carvalho de Melo wrote:
> > Em Thu, Nov 27, 2014 at 11:56:03AM +0100, Ingo Molnar escreveu:
> > > Arnaldo, I suppose the fix will go upstream via your tree, as a 
> > > pull request for v3.18 fixes?

> > Right, I can do that.

> > And I agree with the "expected" for events that are out of the current
> > reordering window, i.e. we can't insert something into previous windows,
> > so those are, humm, what would be a good name:
> > stats->out_of_reordering_window, while stats->reordered, would be for
> > events that were found out of order, but were successfully sorted as
> > part of a flush operation, right?
 
> the forced flush is when we find out we crossed the allowed allocation
> space for the samples queue.. so we take the half of the sorted queue
> and flush it.. for this case we break the flushing logic and we might

Well, we make it more likely than without a forced flush to find out of
order events, because the window suddenly became smaller, its like we
found a FLUSH event right there, no?

> (probably just in theory) get out of order events
 
> but IMO both cases of out of order event are equal.. we dont do
> anything special for forced flushed AFAIK

- Arnaldo

  reply	other threads:[~2014-11-27 14:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 15:39 [PATCH] perf tools: Do not fail on processing out of order event Jiri Olsa
2014-11-26 15:44 ` Arnaldo Carvalho de Melo
2014-11-27 10:56   ` Ingo Molnar
2014-11-27 12:54     ` Jiri Olsa
2014-11-27 13:54       ` Arnaldo Carvalho de Melo
2014-11-27 13:53     ` Arnaldo Carvalho de Melo
2014-11-27 14:07       ` Jiri Olsa
2014-11-27 14:16         ` Arnaldo Carvalho de Melo [this message]
2014-11-27 14:23           ` Jiri Olsa
2014-11-27 14:45             ` Arnaldo Carvalho de Melo
2014-11-27 19:44 ` Andi Kleen
2014-12-09 10:16 ` [tip:perf/urgent] perf session: " tip-bot for Jiri Olsa

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=20141127141626.GK3808@redhat.com \
    --to=acme@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ak@linux.intel.com \
    --cc=cjashfor@linux.vnet.ibm.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    --cc=torvalds@linux-foundation.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