From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Steve Langstaff <steve.langstaff@pebblebay.com>
Cc: "'David Miller'" <davem@davemloft.net>,
paulmck@linux.vnet.ibm.com, mingo@elte.hu,
jwboyer@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
ltt-dev@lists.casi.polymtl.ca,
"'Subrata Modak'" <tosubrata@gmail.com>,
"'Alan D. Brunelle'" <Alan.Brunelle@hp.com>,
"'Andika Triwidada'" <andika@startrek.or.id>
Subject: Re: [ltt-dev] Test module : benchmarking read-side locking speed
Date: Tue, 26 May 2009 09:33:19 -0400 [thread overview]
Message-ID: <20090526133319.GB14851@Krystal> (raw)
* Steve Langstaff (steve.langstaff@pebblebay.com) wrote:
> > From: Mathieu Desnoyers [mailto:compudj@krystal.dyndns.org]
> > Sent: 22 May 2009 16:02
> > To: Steve Langstaff
> > Cc: 'David Miller'; paulmck@linux.vnet.ibm.com; mingo@elte.hu;
> > jwboyer@linux.vnet.ibm.com; linux-kernel@vger.kernel.org; ltt-
> > dev@lists.casi.polymtl.ca; 'Subrata Modak'; 'Alan D. Brunelle'; 'Andika
> > Triwidada'
> > Subject: Re: [ltt-dev] Test module : benchmarking read-side locking
> > speed
> >
> > * Steve Langstaff (steve.langstaff@pebblebay.com) wrote:
> > > > From: Mathieu Desnoyers [mailto:compudj@krystal.dyndns.org]
> > > > Sent: 21 May 2009 20:12
> > >
> > >
> > > > I am trying to complete my numbers for performance impact of read-
> > side
> > > > locking primitives (on the fast path) for various architectures.
> > >
> > > > Help with testing on a larger set of architectures would be more
> > than
> > > > welcome. Note that this module requires the kernel to be configured
> > > > with
> > > > CONFIG_PREEMPT=y. Some config option sanity checking is done at
> > > > compile-time. Other requirement : disable invasive lockdep-style
> > > > instrumentation.
> > >
> > > Another requirement is that get_cycles() needs to return something
> > > meaningful :)
> > >
> >
> > For ARMv7 Omap3, I have the following version (I've been able to get
> > benchmarks with it yesterday). It requires LTTng to be started for the
> > trace clock infrastructure to be in place and running to provide a full
> > 64-bits emulated TSC.
>
> Using your updated test source, I get slightly different results on my
> PXA255 (total time = 1 rather than 0), but I'm not convinced that the
> measurements are correct...
>
The LTTng trace clock only uses the cycle counter on ARM OMAP3, AFAIK.
Therefore, the implementation you use is probably using a jiffy-based
method+logical clock (see asm-generic/trace-clock.h). Therefore those
numbers do not represent cycles.
Thanks,
Mathieu
> /lib/modules/2.6.29.2 # insmod ./ltt_test.ko
> [ 81.372318] test init
> [ 81.374647] Number of active CPUs : 1
> [ 81.378806] test results: time for baseline
> [ 81.383010] number of loops: 20000
> [ 81.386510] total time: 1
> [ 81.389147] -> baseline takes 0 cycles
> [ 81.392910] test end
> [ 81.396017] test results: time for spinlock
> [ 81.400292] number of loops: 20000
> [ 81.403711] total time: 1
> [ 81.406417] -> spinlock takes 0 cycles
> [ 81.410184] test end
> [ 81.413293] test results: time for read rwlock
> [ 81.417825] number of loops: 20000
> [ 81.421248] total time: 1
> [ 81.423887] -> read rwlock takes 0 cycles
> [ 81.427990] test end
> [ 81.430844] test results: time for seqlock
> [ 81.434962] number of loops: 20000
> [ 81.438439] total time: 1
> [ 81.441075] -> seqlock takes 0 cycles
> [ 81.444751] test end
> [ 81.447871] test results: time for preempt disable/enable pairs
> [ 81.453818] number of loops: 20000
> [ 81.457300] total time: 1
> [ 81.459940] -> preempt disable/enable pair takes 0 cycles
> [ 81.465359] test end
> insmod: cannot insert './ltt_test.ko': Resource temporarily unavailable
> (-1): Resource temporarily unavailable
>
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2009-05-26 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 13:33 Mathieu Desnoyers [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-22 15:01 Mathieu Desnoyers
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=20090526133319.GB14851@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=Alan.Brunelle@hp.com \
--cc=andika@startrek.or.id \
--cc=davem@davemloft.net \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=steve.langstaff@pebblebay.com \
--cc=tosubrata@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®