public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric St-Laurent <ericstl34@sympatico.ca>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Tony Lindgren <tony@atomide.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Pavel Machek <pavel@suse.cz>,
	Arjan van de Ven <arjan@infradead.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Andrea Arcangeli <andrea@suse.de>,
	George Anzinger <george@mvista.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	john stultz <johnstul@us.ibm.com>,
	Zwane Mwaikambo <zwane@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Dynamic tick, version 050127-1
Date: Tue, 01 Feb 2005 20:06:51 -0500	[thread overview]
Message-ID: <1107306411.8029.9.camel@orbiter> (raw)
In-Reply-To: <1107289206.18349.16.camel@krustophenia.net>

On Tue, 2005-02-01 at 15:20 -0500, Lee Revell wrote:

> I was wondering how Windows handles high res timers, if at all.  The
> reason I ask is because I have been reverse engineering a Windows ASIO
> driver, and I find that if the latency is set below about 5ms, by

By default, Windows "multimedia" timers have 10ms resolution (this
depends on the exact version of Windows used...).  You can call the
timeBeginPeriod() function to lower the resolution to 1ms.

This resolution seem related to the task scheduler timeslice.  After you
call this function, the Sleep() call has also a resolution of 1ms
instead of 10ms.

I remember reading that the multimedia timers are implemented as a high
priority thread.

You can found more details on this site :

http://www.geisswerks.com/ryan/FAQS/timing.html

Best regards,

Eric St-Laurent



      parent reply	other threads:[~2005-02-02  1:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 21:29 [PATCH] Dynamic tick, version 050127-1 Tony Lindgren
2005-01-27 21:50 ` Tony Lindgren
2005-02-01 11:00 ` Pavel Machek
2005-02-01 20:40   ` Tony Lindgren
2005-02-01 21:25     ` Pavel Machek
2005-02-01 23:03       ` Tony Lindgren
2005-02-02 13:50         ` Pavel Machek
2005-02-02 13:50         ` Pavel Machek
2005-02-02 13:56         ` Pavel Machek
2005-02-02 14:11         ` Pavel Machek
2005-02-03  3:04           ` Tony Lindgren
2005-02-03 10:56             ` Pavel Machek
2005-02-03 16:43               ` Tony Lindgren
2005-02-04  5:19                 ` Tony Lindgren
2005-02-04  6:33                   ` Zwane Mwaikambo
2005-02-04 17:18                     ` Tony Lindgren
2005-02-04 17:31                       ` Zwane Mwaikambo
2005-02-04 17:42                         ` Tony Lindgren
2005-02-04 17:54                           ` Zwane Mwaikambo
2005-02-04 18:58                             ` Tony Lindgren
2005-02-04 19:24                               ` Tony Lindgren
2005-02-05 23:00                   ` Pavel Machek
2005-02-06  2:33                     ` Tony Lindgren
2005-02-06  3:54                       ` Tony Lindgren
2005-02-06  8:41                         ` Pavel Machek
2005-02-06  8:50                         ` Pavel Machek
2005-02-06 17:07                           ` Tony Lindgren
2005-02-06 12:15                         ` Pavel Machek
2005-02-06 17:08                           ` Tony Lindgren
2005-02-06  8:11                       ` Pavel Machek
2005-02-06  8:53                         ` Lee Revell
2005-02-06 10:25                           ` Pavel Machek
2005-02-07 22:08                             ` George Anzinger
2005-02-06 17:10                         ` Tony Lindgren
2005-02-06 18:34                           ` Pavel Machek
2005-02-01 20:20 ` Lee Revell
2005-02-01 23:42   ` Tony Lindgren
2005-02-02  1:06   ` Eric St-Laurent [this message]

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=1107306411.8029.9.camel@orbiter \
    --to=ericstl34@sympatico.ca \
    --cc=andrea@suse.de \
    --cc=arjan@infradead.org \
    --cc=benh@kernel.crashing.org \
    --cc=george@mvista.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rlrevell@joe-job.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=tony@atomide.com \
    --cc=zwane@arm.linux.org.uk \
    /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