[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140619103448.GA7619@krava.brq.redhat.com>
Date: Thu, 19 Jun 2014 12:34:48 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: David Ahern <dsahern@...il.com>
Cc: Jiri Olsa <jolsa@...nel.org>, linux-kernel@...r.kernel.org,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Jean Pihet <jean.pihet@...aro.org>,
Namhyung Kim <namhyung@...nel.org>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCHv2 00/18] perf tools: Factor ordered samples queue
On Wed, Jun 18, 2014 at 01:44:46PM -0600, David Ahern wrote:
SNIP
> >
> >Also now we have one of our big memory spender under control
> >and the ordered events queue code is put in separated object
> >with clear interface ready to be used by another command
> >like script.
> >
> >Also reachable in here:
> > git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
> > perf/core_ordered_events
> >
>
> I've skimmed through the patches. What happens if you are in the middle of a
> round and the max queue size is reached?
half of the queue (time half) is flushed to make some free space
> I need to find some time for a detailed review, and to run through some
> stress case scenarios. e.g., a couple that come to mind
> perf sched record -- perf bench sched pipe
> perf kvm record while booting a nested VM which causes a lot of VMEXITs
will try.. at least the first one ;-)
thanks for looking on this,
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists