From: Clemens Ladisch <clemens@ladisch.de>
To: Henning Thielemann <alsa@henning-thielemann.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: sending a sequencer event to a delayed queue
Date: Wed, 14 Mar 2012 09:22:09 +0100 [thread overview]
Message-ID: <4F605531.6050103@ladisch.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1203132322120.5893@anubis.informatik.uni-halle.de>
Henning Thielemann wrote:
> In order to understand how snd_seq_remove_events works, I looked into
> its source code ... I wondered why I can set the queue as condition
> with snd_seq_remove_events_set_queue but there is no flag that enables
> queue matching
SND_SEQ_REMOVE_DEST enables queue/client/port matching.
> and actually the queue is not checked in remove_match, as far as I can
> see.
Well, it's checked in the kernel. :) I guess this is a bug in alsa-lib.
> I have another question: Is snd_seq_remove_events atomic, that is, if
> some events have the same time stamp, is it guaranteed that they are
> removed all or none at all? Are events still delivered while removing?
Queues are locked one at a time; events in the same queue with the same
timestamping mode should be removed atomically.
Regards,
Clemens
next prev parent reply other threads:[~2012-03-14 8:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 18:20 sending a sequencer event to a delayed queue Henning Thielemann
2012-03-10 20:51 ` Clemens Ladisch
2012-03-11 15:41 ` Henning Thielemann
2012-03-11 20:40 ` Clemens Ladisch
2012-03-11 21:08 ` Henning Thielemann
2012-03-11 22:14 ` Henning Thielemann
2012-03-12 8:21 ` Clemens Ladisch
2012-03-14 20:01 ` Henning Thielemann
2012-03-14 20:22 ` Henning Thielemann
2012-03-14 21:36 ` Clemens Ladisch
2012-03-13 22:33 ` Henning Thielemann
2012-03-14 8:22 ` Clemens Ladisch [this message]
2012-03-14 17:37 ` Henning Thielemann
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=4F605531.6050103@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=alsa@henning-thielemann.de \
/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.