Hi,
Sorry for late..
On Mon, Sep 24, 2018 at 09:32:11PM +0300, Alexey Budankov wrote:
> On 24.09.2018 17:29, Jiri Olsa wrote:
> > On Mon, Sep 24, 2018 at 04:09:09PM +0300, Alexey Budankov wrote:
> >> Command:
> >>
> >> /usr/bin/time ./perf.thr record --threads=T \
> >>-N -B -T -R --call-graph
Hi,
On 03.10.2018 0:41, Jiri Olsa wrote:
> I think we are able to keep it along under --aio option
> together with current (sync) write implementation and
> future threads implementation.. could you make it available
> only under --aio option (or such) and repost?
That's possible. Let me look
On Mon, Sep 24, 2018 at 10:23:37PM +0300, Alexey Budankov wrote:
SNIP
> > Workload: matrix multiplication in 128 threads
> >
> > P (period, ms) : 3
> > runtime overhead (%) : 1.8x ~ 12.58 / 6.81
> > data loss (%): 9
> > LOST events : 147
> > SAMPLE even
Hi,
On 21.09.2018 15:15, Alexey Budankov wrote:
> Hello Jiri,
>
> On 21.09.2018 9:13, Alexey Budankov wrote:
>> Hello Jiri,
>>
>> On 14.09.2018 12:37, Alexey Budankov wrote:
>>> On 14.09.2018 11:28, Jiri Olsa wrote:
On Fri, Sep 14, 2018 at 10:26:53AM +0200, Jiri Olsa wrote:
SNIP
>>
Hi,
On 24.09.2018 21:32, Alexey Budankov wrote:
> Hi,
>
> On 24.09.2018 17:29, Jiri Olsa wrote:
>> On Mon, Sep 24, 2018 at 04:09:09PM +0300, Alexey Budankov wrote:
>>> Hi,
>>>
>>> On 24.09.2018 10:02, Alexey Budankov wrote:
Hi,
On 23.09.2018 22:30, Jiri Olsa wrote:
> On Fri, Se
Hi,
On 24.09.2018 17:29, Jiri Olsa wrote:
> On Mon, Sep 24, 2018 at 04:09:09PM +0300, Alexey Budankov wrote:
>> Hi,
>>
>> On 24.09.2018 10:02, Alexey Budankov wrote:
>>> Hi,
>>>
>>> On 23.09.2018 22:30, Jiri Olsa wrote:
On Fri, Sep 21, 2018 at 09:13:08AM +0300, Alexey Budankov wrote:
>>>
On Mon, Sep 24, 2018 at 04:09:09PM +0300, Alexey Budankov wrote:
> Hi,
>
> On 24.09.2018 10:02, Alexey Budankov wrote:
> > Hi,
> >
> > On 23.09.2018 22:30, Jiri Olsa wrote:
> >> On Fri, Sep 21, 2018 at 09:13:08AM +0300, Alexey Budankov wrote:
> >>
> >> SNIP
> >>
> >>> Events:
> >>> cpu/period=P,e
Hi,
On 24.09.2018 10:02, Alexey Budankov wrote:
> Hi,
>
> On 23.09.2018 22:30, Jiri Olsa wrote:
>> On Fri, Sep 21, 2018 at 09:13:08AM +0300, Alexey Budankov wrote:
>>
>> SNIP
>>
>>> Events:
>>> cpu/period=P,event=0x3c/Duk;CPU_CLK_UNHALTED.THREAD
>>> cpu/period=P,umask=0x3/Duk;CPU_CLK_UNHALTED.REF
Hi,
On 23.09.2018 22:30, Jiri Olsa wrote:
> On Fri, Sep 21, 2018 at 09:13:08AM +0300, Alexey Budankov wrote:
>
> SNIP
>
>> Events:
>> cpu/period=P,event=0x3c/Duk;CPU_CLK_UNHALTED.THREAD
>> cpu/period=P,umask=0x3/Duk;CPU_CLK_UNHALTED.REF_TSC
>> cpu/period=P,event=0xc0/Duk;INST_RETIRED.ANY
>> cpu/
On Fri, Sep 21, 2018 at 09:13:08AM +0300, Alexey Budankov wrote:
SNIP
> Events:
> cpu/period=P,event=0x3c/Duk;CPU_CLK_UNHALTED.THREAD
> cpu/period=P,umask=0x3/Duk;CPU_CLK_UNHALTED.REF_TSC
> cpu/period=P,event=0xc0/Duk;INST_RETIRED.ANY
> cpu/period=0xaae61,event=0xc2,umask=0x10/uk;UOPS_RETIRED.ALL
Hello Jiri,
On 21.09.2018 9:13, Alexey Budankov wrote:
> Hello Jiri,
>
> On 14.09.2018 12:37, Alexey Budankov wrote:
>> On 14.09.2018 11:28, Jiri Olsa wrote:
>>> On Fri, Sep 14, 2018 at 10:26:53AM +0200, Jiri Olsa wrote:
>>>
>>> SNIP
>>>
>> The threaded monitoring currently can't monitor back
Hello Jiri,
On 14.09.2018 12:37, Alexey Budankov wrote:
> On 14.09.2018 11:28, Jiri Olsa wrote:
>> On Fri, Sep 14, 2018 at 10:26:53AM +0200, Jiri Olsa wrote:
>>
>> SNIP
>>
> The threaded monitoring currently can't monitor backward maps
> and there are probably more limitations which I have
> In big picture this patchset adds perf record --threads
> option that allows to create threads in following modes:
>
> 1) single thread mode (current)
>
> $ perf record ...
> $ perf record --threads=1 ...
>
> - all maps are read/stored under process thread
>
> 2) mode with specific (X)
* Jiri Olsa wrote:
> On Fri, Sep 14, 2018 at 02:13:07PM +0200, Ingo Molnar wrote:
> >
> > * Peter Zijlstra wrote:
> >
> > > On Fri, Sep 14, 2018 at 01:47:25PM +0200, Jiri Olsa wrote:
> > > > On Fri, Sep 14, 2018 at 01:15:28PM +0200, Peter Zijlstra wrote:
> > > > > On Fri, Sep 14, 2018 at 11:
On Fri, Sep 14, 2018 at 02:13:07PM +0200, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
> > On Fri, Sep 14, 2018 at 01:47:25PM +0200, Jiri Olsa wrote:
> > > On Fri, Sep 14, 2018 at 01:15:28PM +0200, Peter Zijlstra wrote:
> > > > On Fri, Sep 14, 2018 at 11:40:22AM +0200, Ingo Molnar wrote:
> >
* Peter Zijlstra wrote:
> On Fri, Sep 14, 2018 at 01:47:25PM +0200, Jiri Olsa wrote:
> > On Fri, Sep 14, 2018 at 01:15:28PM +0200, Peter Zijlstra wrote:
> > > On Fri, Sep 14, 2018 at 11:40:22AM +0200, Ingo Molnar wrote:
> > > > In fact keeping the files separate has scalability advantages for '
On Fri, Sep 14, 2018 at 01:47:25PM +0200, Jiri Olsa wrote:
> On Fri, Sep 14, 2018 at 01:15:28PM +0200, Peter Zijlstra wrote:
> > On Fri, Sep 14, 2018 at 11:40:22AM +0200, Ingo Molnar wrote:
> > > In fact keeping the files separate has scalability advantages for 'perf
> > > report' and similar
> >
On Fri, Sep 14, 2018 at 01:15:28PM +0200, Peter Zijlstra wrote:
> On Fri, Sep 14, 2018 at 11:40:22AM +0200, Ingo Molnar wrote:
> > In fact keeping the files separate has scalability advantages for 'perf
> > report' and similar
> > parsing tools: they could read all the streams in a per-CPU fashio
On Fri, Sep 14, 2018 at 11:40:22AM +0200, Ingo Molnar wrote:
> In fact keeping the files separate has scalability advantages for 'perf
> report' and similar
> parsing tools: they could read all the streams in a per-CPU fashion already,
> from the very
> beginning.
Also writing to different fil
* Jiri Olsa wrote:
> On Fri, Sep 14, 2018 at 11:29:10AM +0900, Namhyung Kim wrote:
> > On Thu, Sep 13, 2018 at 07:10:35PM +0300, Alexey Budankov wrote:
> > > Hi,
> >
> > Hello,
> >
> > >
> > > On 13.09.2018 15:54, Jiri Olsa wrote:
> > > > hi,
> > > > sending *RFC* for threads support in perf
On 14.09.2018 11:28, Jiri Olsa wrote:
> On Fri, Sep 14, 2018 at 10:26:53AM +0200, Jiri Olsa wrote:
>
> SNIP
>
The threaded monitoring currently can't monitor backward maps
and there are probably more limitations which I haven't spotted
yet.
So far I tested on laptop:
* Namhyung Kim wrote:
> > > The perf.data stays as a single file.
>
> I'm not sure we really need to keep it as a single file. As it's a
> kind of big changes, we might consider breaking compatibility and use
> a directory structure.
Agreed - and to make use of the highly scalable Linux VFS
On Fri, Sep 14, 2018 at 10:26:53AM +0200, Jiri Olsa wrote:
SNIP
> > > The threaded monitoring currently can't monitor backward maps
> > > and there are probably more limitations which I haven't spotted
> > > yet.
> > >
> > > So far I tested on laptop:
> > > http://people.redhat.com/~jolsa/reco
On Thu, Sep 13, 2018 at 07:10:35PM +0300, Alexey Budankov wrote:
> Hi,
>
> On 13.09.2018 15:54, Jiri Olsa wrote:
> > hi,
> > sending *RFC* for threads support in perf record command.
> >
> > In big picture this patchset adds perf record --threads
> > option that allows to create threads in follow
On Fri, Sep 14, 2018 at 11:29:10AM +0900, Namhyung Kim wrote:
> On Thu, Sep 13, 2018 at 07:10:35PM +0300, Alexey Budankov wrote:
> > Hi,
>
> Hello,
>
> >
> > On 13.09.2018 15:54, Jiri Olsa wrote:
> > > hi,
> > > sending *RFC* for threads support in perf record command.
> > >
> > > In big pictur
Hi Namhyung,
On 14.09.2018 5:29, Namhyung Kim wrote:
> On Thu, Sep 13, 2018 at 07:10:35PM +0300, Alexey Budankov wrote:
>> Hi,
>
> Hello,
>
>>
>> On 13.09.2018 15:54, Jiri Olsa wrote:
>>> hi,
>>> sending *RFC* for threads support in perf record command.
>>>
>>> In big picture this patchset adds
On Thu, Sep 13, 2018 at 07:10:35PM +0300, Alexey Budankov wrote:
> Hi,
Hello,
>
> On 13.09.2018 15:54, Jiri Olsa wrote:
> > hi,
> > sending *RFC* for threads support in perf record command.
> >
> > In big picture this patchset adds perf record --threads
> > option that allows to create threads
Hi,
On 13.09.2018 15:54, Jiri Olsa wrote:
> hi,
> sending *RFC* for threads support in perf record command.
>
> In big picture this patchset adds perf record --threads
> option that allows to create threads in following modes:
>
> 1) single thread mode (current)
>
> $ perf record ...
> $ pe
hi,
sending *RFC* for threads support in perf record command.
In big picture this patchset adds perf record --threads
option that allows to create threads in following modes:
1) single thread mode (current)
$ perf record ...
$ perf record --threads=1 ...
- all maps are read/stored under p
29 matches
Mail list logo