From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-sound@vger.kernel.org
Subject: Re: Bad MIDI performance : 10ms latency instead of the expected
Date: Thu, 26 Aug 1999 20:20:52 +0000 [thread overview]
Message-ID: <marc-linux-sound-93570211709133@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93568883025986@msgid-missing>
> > 200bytes/sec is just rudiculous , how do you plan to drive an external synth
> > with that little MIDI bandwidth ?
>
> I need a timer around 2000Hz for some good code. I won't support polling
> mode (busy loop) in any case.
Then your code will never be usable. Some hardware sucks, you have to do
limited polling with a timer backoff. A well tuned polling loop will often
work out nicely providing you are careful. Remember with irqs on you are
just like busy in userspace no worse. You can even do
while(poll_input()=0)
{
if(current->need_resched())
schedule();
}
sort of stuff
next prev parent reply other threads:[~1999-08-26 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-26 17:34 Bad MIDI performance : 10ms latency instead of the expected 1-1.5ms Benno Senoner
1999-08-26 18:42 ` Bad MIDI performance : 10ms latency instead of the expected Jaroslav Kysela
1999-08-26 19:38 ` Bad MIDI performance : 10ms latency instead of the expected 1-1.5ms Benno Senoner
1999-08-26 20:20 ` Alan Cox [this message]
1999-08-26 20:41 ` Bad MIDI performance : 10ms latency instead of the expected Alan Cox
1999-08-26 20:42 ` Bad MIDI performance : 10ms latency instead of the expected 1-1.5ms Benno Senoner
1999-08-26 20:51 ` Bad MIDI performance : 10ms latency instead of the expected Jaroslav Kysela
1999-08-26 21:04 ` Alan Cox
1999-08-26 21:53 ` Benno Senoner
1999-09-18 21:26 ` Bad MIDI performance : 10ms latency instead of the expected 1-1.5ms Peter Enderborg
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=marc-linux-sound-93570211709133@msgid-missing \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-sound@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