From: Parag Warudkar <kernel-stuff@comcast.net>
To: puneet_kaushik@persistent.co.in
Cc: linux-kernel@vger.kernel.org
Subject: Re: Needed faster implementation of do_gettimeofday()
Date: Sun, 20 Feb 2005 10:48:00 -0500 [thread overview]
Message-ID: <200502201048.01424.kernel-stuff@comcast.net> (raw)
In-Reply-To: <34373.203.199.147.2.1108897097.squirrel@webmail.persistent.co.in>
On Sunday 20 February 2005 05:58 am, puneet_kaushik@persistent.co.in wrote:
> 985913 8.6083 vmlinux mark_offset_tsc
> 584473 5.1032 libc-2.3.2.so getc
What makes you think mark_offset_tsc is slow? Do you have any comparative
numbers? It might just be that the workload you are throwing at it justifies
it. (For e.g. if your workload does a zillion system calls, system_call will
show up as a hot spot in oprofile - doesn't necessarily mean it is slow -
it's just overused.) Can you post the relevant code?
Parag
next prev parent reply other threads:[~2005-02-20 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 10:58 Needed faster implementation of do_gettimeofday() puneet_kaushik
2005-02-20 15:48 ` Parag Warudkar [this message]
2005-02-22 3:06 ` George Anzinger
2005-02-22 13:56 ` Puneet Kaushik
2005-02-22 15:46 ` Chris Friesen
2005-02-22 16:44 ` George Anzinger
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=200502201048.01424.kernel-stuff@comcast.net \
--to=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=puneet_kaushik@persistent.co.in \
/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