All of lore.kernel.org
 help / color / mirror / Atom feed
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:12:31 -0500	[thread overview]
Message-ID: <75b66ecd0703011412l513be986l5ea67d8c8e47e66b@mail.gmail.com> (raw)
In-Reply-To: <70a871c80703010923l1cd70240n4a993ef4a2a60c3f@mail.gmail.com>

On 3/1/07, Dmitry Baikov <dsbaikov@gmail.com> wrote:
> And since I already rewritten this code with snd_seq_ev_set_direct() +
> poll(), I have a question:
> Does queue + snd_seq_ev_schedule_real() offer better real resolution
> than poll (which gives 1 ms)?

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.

Anyway mainline Linux kernel has hrtimers now.  So shouldn't the
resolution of all timeouts be much better than 1ms?

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

  parent reply	other threads:[~2007-03-01 22:12 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 [this message]
2007-03-01 22:14       ` Dmitry Baikov
2007-03-01 22:17         ` Lee Revell
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=75b66ecd0703011412l513be986l5ea67d8c8e47e66b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.