From: trajber@gmail.com (Mauro Romano Trajber)
To: kernelnewbies@lists.kernelnewbies.org
Subject: syscalls performance
Date: Fri, 25 Feb 2011 17:30:32 -0300 [thread overview]
Message-ID: <AANLkTimdHuw7SDuLCbsLHcLvVhv9XSNWwyFOOzzdfX9v@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=S0just=K_+_OJspgceX2T7-xtiRos4AQU6xA+@mail.gmail.com>
Sure, the code is attached.
On Fri, Feb 25, 2011 at 5:15 PM, Daniel Baluta <daniel.baluta@gmail.com>wrote:
> On Fri, Feb 25, 2011 at 8:22 PM, Mauro Romano Trajber <trajber@gmail.com>
> wrote:
> > Thanks Enrico and Daniel, you're right. glibc was caching getpid(); but
> this
> > is not the root cause of this behavior.
> > Going further, I decide to use call getpid without glibc, using
> > syscall(SYS_getpid) to test this behavior and it happened again.
> > Calling it once, the test consumes about 7k CPU cycles and 10 calls
> consumes
> > about 10k CPU cycles.
> > Any ideas ?
>
> Can you post a pointer to your code and information about how you got
> this numbers?
>
> thanks,
> Daniel.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110225/f273b11b/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: syscallperf.c
Type: text/x-csrc
Size: 732 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110225/f273b11b/attachment.bin
next prev parent reply other threads:[~2011-02-25 20:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 17:03 syscalls performance Mauro Romano Trajber
2011-02-25 17:15 ` Daniel Baluta
2011-02-25 18:22 ` Mauro Romano Trajber
2011-02-25 20:15 ` Daniel Baluta
2011-02-25 20:30 ` Mauro Romano Trajber [this message]
2011-02-25 20:42 ` Enrico Granata
2011-02-25 20:59 ` Jim Kukunas
2011-02-25 21:00 ` Enrico Granata
2011-02-25 22:03 ` Mauro Romano Trajber
2011-02-25 22:06 ` Daniel Baluta
2011-02-25 22:14 ` Enrico Granata
2011-02-26 4:31 ` Mulyadi Santosa
[not found] <D3CBA33B-3809-4AF5-9F66-0F2D256C4A82@cs.ucsd.edu>
2011-02-25 17:14 ` Enrico Granata
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=AANLkTimdHuw7SDuLCbsLHcLvVhv9XSNWwyFOOzzdfX9v@mail.gmail.com \
--to=trajber@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).