From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: the state of the concurrency branch
Date: Tue, 27 Aug 2013 22:31:25 -0600 [thread overview]
Message-ID: <87eh9exwpu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83a9k2fo0x.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 28 Aug 2013 07:16:30 +0300")
>> The current code only allows a single thread running at a time.
Eli> Really? How does it do that?
Only one thread can run Lisp at a time.
Threads not running Lisp can do other things, though currently this amounts
to waiting for I/O or blocking on a mutex.
This is implemented using a global lock.
Eli> Anyway, if that's true, threads will be much less useful than they
Eli> could be (e.g., fetching a large newsgroup while editing would be
Eli> impossible, right?). Also, the implementation of condition variables
Eli> could be much simpler and dumber than I imagined.
I am not sure whether it would work.
System level condition variables are used in thread-join.
This is a situation where the code is truly multi-threaded -- multiple
threads can be waiting to see another thread exit; they will
serialize only when re-entering Lisp.
Fetching while editing can work fine.
Tom
next prev parent reply other threads:[~2013-08-28 4:31 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 19:26 the state of the concurrency branch Tom Tromey
2013-08-25 19:36 ` Paul Eggert
2013-08-25 19:43 ` Tom Tromey
2013-08-25 20:02 ` Paul Eggert
2013-08-26 14:55 ` Tom Tromey
2013-08-25 20:30 ` Tom Tromey
2013-08-26 16:48 ` Stefan Monnier
2013-08-26 17:04 ` Juanma Barranquero
2013-08-26 17:19 ` Tom Tromey
2013-08-26 18:51 ` Eli Zaretskii
2013-08-26 21:29 ` Stefan Monnier
2013-08-27 2:30 ` Tom Tromey
2013-08-27 16:08 ` Eli Zaretskii
2013-08-27 18:05 ` Paul Eggert
2013-08-27 18:23 ` Tom Tromey
2013-08-27 18:39 ` Paul Eggert
2013-08-27 18:46 ` Tom Tromey
2013-08-27 18:52 ` Paul Eggert
2013-08-27 19:08 ` Eli Zaretskii
2013-08-27 19:12 ` Paul Eggert
2013-08-27 18:26 ` Eli Zaretskii
2013-08-27 19:14 ` Tom Tromey
2013-08-27 19:24 ` Eli Zaretskii
2013-08-27 19:29 ` Tom Tromey
2013-08-28 0:50 ` Stefan Monnier
2013-08-28 4:16 ` Eli Zaretskii
2013-08-28 4:31 ` Tom Tromey [this message]
2013-08-28 4:58 ` Eli Zaretskii
2013-08-28 13:21 ` Stefan Monnier
2013-08-28 13:48 ` Tom Tromey
2013-08-28 14:27 ` Stefan Monnier
2013-08-28 16:23 ` Eli Zaretskii
2013-08-29 3:54 ` Tom Tromey
2013-08-29 15:10 ` Eli Zaretskii
2013-08-31 9:57 ` Eli Zaretskii
2013-08-31 11:51 ` Eli Zaretskii
2013-08-31 13:42 ` Eli Zaretskii
2013-09-01 15:49 ` Eli Zaretskii
2013-09-02 15:27 ` Eli Zaretskii
2013-08-28 0:45 ` Stefan Monnier
2013-08-28 2:34 ` Tom Tromey
2013-08-27 18:33 ` Tom Tromey
2013-08-28 15:58 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2013-10-16 18:24 Barry OReilly
2013-10-16 20:25 ` Barry OReilly
2013-10-18 1:41 ` Tom Tromey
2013-10-18 3:32 ` Tom Tromey
2013-10-18 18:13 ` Stefan Monnier
2013-10-18 18:16 ` Tom Tromey
2013-10-19 18:41 ` Richard Stallman
2013-10-19 19:29 ` Barry OReilly
2013-10-19 21:42 ` Stefan Monnier
2013-10-20 0:41 ` Barry OReilly
2013-10-21 15:08 ` Tom Tromey
2013-10-21 16:07 ` Barry OReilly
2013-10-21 18:17 ` Stefan Monnier
2013-10-21 16:41 ` Stefan Monnier
2013-10-19 20:21 ` Barry OReilly
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eh9exwpu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).