From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: djurfeldt@nada.kth.se
Subject: Re: Warning: Unstable POSIX threads support comitted to CVS
Date: Mon, 09 Dec 2002 18:40:40 +0100 [thread overview]
Message-ID: <xy71y4r6qg7.fsf@nada.kth.se> (raw)
In-Reply-To: <ljr8cruv44.fsf@burns.dt.e-technik.uni-dortmund.de> (Marius Vollmer's message of "09 Dec 2002 15:26:03 +0100")
Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
> Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
>
>> It is very irritating that signals are delivered to whatever thread
>> happens to run for the moment.
>
> Do you refer to the execution of POSIX signal handlers or to the
> execution of Scheme signal handlers?
With "delivered" I'm thinking of "end-point" delivery, that is
execution of Scheme signal handlers. I'm thinking of channeling all
signals to a particular target thread (which becomes the one to run
its handlers until the target is switched).
> That is, signals-plus-threads are quite nasty on Linux. I think we
> should have a dedicated signal handling thread that polls for signals
> and marks the relevant system asyncs when they arrive.
That sounds like a good solution. Are there particular reasons why a
dedicated thread is needed rather than that an arbitrary POSIX signal
handler of an arbitrary receives the signal sets the asyncs of the
"foreground" thread?
I guess one such reason could be that we, in that case, could block
signals for all threads except the signal one, with the benefit that a
particular signal is only received "once" (rather than getting a
"barrage" of async marks at asyncronous points in time), right?
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-12-09 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 13:44 Warning: Unstable POSIX threads support comitted to CVS Mikael Djurfeldt
2002-12-09 14:26 ` Marius Vollmer
2002-12-09 17:40 ` Mikael Djurfeldt [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xy71y4r6qg7.fsf@nada.kth.se \
--to=djurfeldt@nada.kth.se \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).