From: tobias@gambas-buch.de (Tobias Boege)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Speed Analysis Util.
Date: Sat, 8 Dec 2012 16:58:50 +0100 [thread overview]
Message-ID: <20121208155850.GD543@aurora> (raw)
In-Reply-To: <CAHPT9mbxAoUgB9enc06zU1ze92-=rT_k5GVkPT=4q14WaMy9Eg@mail.gmail.com>
On Sat, 08 Dec 2012, Gustavo da Silva wrote:
> Hello Kernel Brothers!! How are you???
>
> So, I would like test the performance of my notebook, developing one or two
> utilities, and have a better
> mensurement about the speed.
>
> But it can help all of us.
>
> 1st: I would like mensure the speed making a counter (exacly bogomips? may
> be). Loop+counter during 1 tickrate.
> 2nd: The most interesting: How many memory cells in ram can we
> access during 1tickrate? How could we develop this?!
>
> Both utils may run in long mode (64bits). Well, in real mode too; so, we
> can compare the speed in the two modes!
>
> Some one knows how to develop a very small program/routine about that?!
>
> For the 2nd situation, a simple idea wrote in codesnipet form (consider the
> intention, not the sintax! there are bugs! I know. Intel syntax.)
Obviously! ;-)
>
> dw the_counter_cell 0
> lea bx, the_counter_cell
> xor bx,bx
> label:
> inc [bx] # Could not be so simple like this, because the address can
> be cached. Right?
> loop label # breaked by an interruption. Just to express the intention.
>
> How could we create a small code for the 2nd situation, tring to force the
> processor to not use the cache?
As Drepper says[0], use the movntq instruction on x86_64 to bypass the
cache.
Regards,
Tobi
[0] http://www.akkadia.org/drepper/cpumemory.pdf p. 47ff.
next prev parent reply other threads:[~2012-12-08 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 14:22 Speed Analysis Util Gustavo da Silva
2012-12-08 14:25 ` Gustavo da Silva
2012-12-08 15:58 ` Tobias Boege [this message]
2012-12-10 12:21 ` Gustavo da Silva
[not found] ` <CA+4BDG6JPqMw2+76Vt268Np6Xqo=akp69_mnwswXMmQ=grzV6Q@mail.gmail.com>
2012-12-11 13:19 ` Gustavo da Silva
2012-12-11 16:27 ` Tobias Boege
2012-12-11 17:05 ` Gustavo da Silva
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=20121208155850.GD543@aurora \
--to=tobias@gambas-buch.de \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.