From: "Lee Revell" <rlrevell@joe-job.com>
To: Dmitry Baikov <dsbaikov@gmail.com>
Cc: Jack Dev List <jackit-devel@lists.sourceforge.net>,
alsa-devel@lists.sourceforge.net
Subject: Re: [Jackit-devel] alsaseq reorders my events
Date: Thu, 1 Mar 2007 17:17:39 -0500 [thread overview]
Message-ID: <75b66ecd0703011417p66637a9duaa59a3f19251ba68@mail.gmail.com> (raw)
In-Reply-To: <70a871c80703011414u4f084a13o563184458382fcba@mail.gmail.com>
On 3/1/07, Dmitry Baikov <dsbaikov@gmail.com> wrote:
> On 3/2/07, Lee Revell <rlrevell@joe-job.com> wrote:
> > On older kernels it depends on whether ALSA sequencer is configured to
> > use RTC or regular kernel timers. And poll() resolution is 4ms by
> > default (HZ=250) not 1ms.
> HZ=1000 here :)
>
> > Anyway mainline Linux kernel has hrtimers now. So shouldn't the
> > resolution of all timeouts be much better than 1ms?
>
> poll() has 1ms resolution by design (API) :(
>
Hmm then I would consider using whatever userspace API hrtimers expose
if it's acceptable to require a recent kernel (or you don't mind
implementing lower resolution for legacy systems).
Lee
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-01 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 13:35 alsaseq reorders my events Dmitry Baikov
2007-03-01 16:51 ` [Jackit-devel] [Alsa-devel] " Rui Nuno Capela
2007-03-01 16:59 ` [Jackit-devel] " Clemens Ladisch
2007-03-01 17:23 ` Dmitry Baikov
2007-03-01 22:02 ` Rui Nuno Capela
2007-03-01 22:12 ` Lee Revell
2007-03-01 22:14 ` Dmitry Baikov
2007-03-01 22:17 ` Lee Revell [this message]
2007-03-02 10:35 ` Clemens Ladisch
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=75b66ecd0703011417p66637a9duaa59a3f19251ba68@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=dsbaikov@gmail.com \
--cc=jackit-devel@lists.sourceforge.net \
/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