From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Gerald Grabner <gerald.grabner@gmx.net>,
alsa-devel@lists.sourceforge.net
Subject: Re: seq: maximum number of events w.r.t. ordering in queue
Date: Mon, 05 Feb 2007 19:10:25 +0100 [thread overview]
Message-ID: <1170699026.3324.1173012819@webmail.messagingengine.com> (raw)
In-Reply-To: <45C62E51.3050608@gmx.net>
Gerald Grabner wrote:
> for simultaneously playing many midi tracks each with a large number
> of events, it would be convenient to output one track after the other
> in a simple loop, without caring about the ordering of the events.
>
> Of course, this requires an output buffer large enough to hold all
> events, otherwise events of the later are postponed every time the
> buffer is full. But one question remains, at least for me:
> Is there a maximum number of events w.r.t. the ordering in a queue?
Yes. Your client buffer can have any size, but the events stored in the
kernel for a queue are sent from an interrupt handler and must therefore
be in locked kernel memory. The kernel buffer is currently restricted
to 2000 events for one client.
Regards,
Clemens
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2007-02-05 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 19:04 seq: maximum number of events w.r.t. ordering in queue Gerald Grabner
2007-02-05 18:10 ` Clemens Ladisch [this message]
2007-02-05 20:07 ` Gerald Grabner
2007-02-06 11:59 ` Clemens Ladisch
2007-02-06 20:40 ` Gerald Grabner
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=1170699026.3324.1173012819@webmail.messagingengine.com \
--to=cladisch@fastmail.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=gerald.grabner@gmx.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.