From: Willy Tarreau <willy@w.ods.org>
To: dean gaudet <dean-list-linux-kernel@arctic.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_X86_PM_TIMER is slow
Date: Fri, 12 Nov 2004 07:04:14 +0100 [thread overview]
Message-ID: <20041112060413.GF783@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.61.0411112143200.1846@twinlark.arctic.org>
Hi,
On Thu, Nov 11, 2004 at 09:52:27PM -0800, dean gaudet wrote:
> when using CONFIG_X86_PM_TIMER i'm finding that gettimeofday() calls take
> 2.8us on a p-m 1.4GHz box... which is an order of magnitude slower than
> TSC-based solutions.
>
> on one workload i'm seeing a 7% perf improvement by booting "acpi=off" to
> force it to use tsc instead of the PM timer... (the workload calls
> gettimeofday too frequently, but i can't change that).
I did not test, this might be interesting.
In fact, what would be very good would be sort of a new select/poll/epoll
syscalls with an additional argument, which would point to a structure
that the syscall would fill in return with the time of day. This would
greatly reduce the number of calls to gettimeofday() in some programs,
and make use of the time that was used by the syscall itself.
For example, if I could call it like this, it would be really cool :
ret = select_absdate(&in, &out, &excp, &date_timeout, &return_date);
with <date_timeout> the date at which to timeout (instead of the number of
microseconds) and <return_date> the current date upon return.
Cheers,
Willy
next prev parent reply other threads:[~2004-11-12 6:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 5:52 CONFIG_X86_PM_TIMER is slow dean gaudet
2004-11-12 6:04 ` Willy Tarreau [this message]
2004-11-12 6:16 ` dean gaudet
2004-11-12 7:06 ` Willy Tarreau
2004-11-12 7:43 ` dean gaudet
2004-11-12 10:07 ` Willy Tarreau
2004-11-16 8:10 ` 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=20041112060413.GF783@alpha.home.local \
--to=willy@w.ods.org \
--cc=dean-list-linux-kernel@arctic.org \
--cc=linux-kernel@vger.kernel.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