* Jiri Olsa wrote:
> On Tue, Oct 24, 2017 at 02:59:44PM +0200, Ingo Molnar wrote:
> >
> > * Jiri Olsa wrote:
> >
> > > I recently made some changes on threaded record, which are based
> > > on Namhyungs time* API, which is needed to read/sort the data afterwards
> > >
> > > but I wasn't able
On Wed, Oct 25, 2017 at 11:35:39AM +0900, Namhyung Kim wrote:
> Hi Ingo,
>
> On Tue, Oct 24, 2017 at 03:25:23PM +0200, Ingo Molnar wrote:
> >
> > * Arnaldo Carvalho de Melo wrote:
> >
> > > Em Tue, Oct 24, 2017 at 02:59:44PM +0200, Ingo Molnar escreveu:
> > > >
> > > > * Jiri Olsa wrote:
> >
On Tue, Oct 24, 2017 at 02:59:44PM +0200, Ingo Molnar wrote:
>
> * Jiri Olsa wrote:
>
> > I recently made some changes on threaded record, which are based
> > on Namhyungs time* API, which is needed to read/sort the data afterwards
> >
> > but I wasn't able to get any substantial and constant r
Hi Ingo,
On Tue, Oct 24, 2017 at 03:25:23PM +0200, Ingo Molnar wrote:
>
> * Arnaldo Carvalho de Melo wrote:
>
> > Em Tue, Oct 24, 2017 at 02:59:44PM +0200, Ingo Molnar escreveu:
> > >
> > > * Jiri Olsa wrote:
> > >
> > > > I recently made some changes on threaded record, which are based
> >
* Jiri Olsa wrote:
> I recently made some changes on threaded record, which are based
> on Namhyungs time* API, which is needed to read/sort the data afterwards
>
> but I wasn't able to get any substantial and constant reduce of LOST events
> and then I got sidetracked and did not finish, but i
Em Tue, Oct 24, 2017 at 02:59:44PM +0200, Ingo Molnar escreveu:
>
> * Jiri Olsa wrote:
>
> > I recently made some changes on threaded record, which are based
> > on Namhyungs time* API, which is needed to read/sort the data afterwards
> >
> > but I wasn't able to get any substantial and constan
* Arnaldo Carvalho de Melo wrote:
> Em Tue, Oct 24, 2017 at 02:59:44PM +0200, Ingo Molnar escreveu:
> >
> > * Jiri Olsa wrote:
> >
> > > I recently made some changes on threaded record, which are based
> > > on Namhyungs time* API, which is needed to read/sort the data afterwards
> > >
> > >
> On Tue, Oct 24, 2017 at 11:22:00AM +0200, Ingo Molnar wrote:
> >
> > * Liang, Kan wrote:
> >
> > > For 'all', do you mean the whole process?
> >
> > Yeah.
> >
> > > I think that's the ultimate goal. Eventually there will be per-CPU
> > > recording threads created at the beginning of perf record
On Tue, Oct 24, 2017 at 11:22:00AM +0200, Ingo Molnar wrote:
>
> * Liang, Kan wrote:
>
> > For 'all', do you mean the whole process?
>
> Yeah.
>
> > I think that's the ultimate goal. Eventually there will be per-CPU
> > recording
> > threads created at the beginning of perf record and go thr
* Liang, Kan wrote:
> For 'all', do you mean the whole process?
Yeah.
> I think that's the ultimate goal. Eventually there will be per-CPU recording
> threads created at the beginning of perf record and go through the whole
> process.
> The plan is to do the multithreading step by step from
> Em Mon, Oct 23, 2017 at 01:43:39PM +, Liang, Kan escreveu:
> > The plan is to do the multithreading step by step from the simplest case.
> > Synthesizing stage is just a start.
>
> > Only for synthesizing stage, I think the patch series should already
> > cover all the 'synthesizing' steps w
Em Mon, Oct 23, 2017 at 01:43:39PM +, Liang, Kan escreveu:
> The plan is to do the multithreading step by step from the simplest case.
> Synthesizing stage is just a start.
> Only for synthesizing stage, I think the patch series should already cover
> all the
> 'synthesizing' steps which can
> * kan.li...@intel.com wrote:
>
> > The latency is the time cost of __machine__synthesize_threads or its
> > multithreading replacement, record__multithread_synthesize.
> >
> > Original: original single thread synthesize
> > With patch(not merge): multithread synthesize without fina
* kan.li...@intel.com wrote:
> The latency is the time cost of __machine__synthesize_threads or
> its multithreading replacement, record__multithread_synthesize.
>
> Original: original single thread synthesize
> With patch(not merge): multithread synthesize without final file merge
From: Kan Liang
The event synthesization multithreading is introduced in
("perf top optimization") https://lkml.org/lkml/2017/9/29/269
But it was not enabled for perf record. Because the process function
process_synthesized_event was not multithreading friendly.
The patch series temporarily stor
15 matches
Mail list logo
