From: Spencer Baugh <sbaugh@janestreet.com>
To: emacs-devel@gnu.org
Subject: Re: Releasing the thread global_lock from the module API
Date: Fri, 01 Mar 2024 14:51:01 -0500 [thread overview]
Message-ID: <ierzfvhspcq.fsf@janestreet.com> (raw)
In-Reply-To: 868r31rbxn.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Cc: emacs-devel@gnu.org
>> Date: Fri, 01 Mar 2024 14:02:24 -0500
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>> >> > I think this is already possible, see above. I guess I'm missing
>> >> > something.
>> >>
>> >> I don't think it is. How would a module release global_lock, call a C
>> >> library function on the current thread, and then re-acquire the global
>> >> lock? Can you say how you would do that with the APIs we have today?
>> >
>> > If a thread releases a global lock, it cannot run the Lisp machine
>> > until it re-acquire the global lock.
>>
>> Yes. But calling a C library function (by some other library not
>> related to Emacs but used by the module) does not involve calling into
>> the Lisp machine or any Emacs machinery.
>
> There's very little you can do usefully this way without touching some
> aspect of the Lisp machine. Assuming that what you do has some
> relevance to the Emacs session, of course.
Actually, there is lots of useful stuff that can be done this way.
For example, if a C library internally opens a network socket and sends
a request to a network service, that does not touch the Lisp machine and
so can be done this way.
Is that not useful? Or do these touch the Lisp machine in some way I
don't know about?
Since it's useful for me, I'd like to write a patch which allow modules
to do this; would it be considered?
next prev parent reply other threads:[~2024-03-01 19:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 14:53 Releasing the thread global_lock from the module API Spencer Baugh
2024-03-01 16:47 ` Eli Zaretskii
2024-03-01 17:34 ` Spencer Baugh
2024-03-01 18:44 ` Eli Zaretskii
2024-03-01 19:02 ` Spencer Baugh
2024-03-01 19:26 ` Eli Zaretskii
2024-03-01 19:51 ` Spencer Baugh [this message]
2024-03-01 20:42 ` Eli Zaretskii
2024-03-01 21:21 ` Spencer Baugh
2024-03-01 21:34 ` Eli Zaretskii
2024-03-01 21:56 ` Spencer Baugh
2024-03-02 6:43 ` Eli Zaretskii
2024-03-02 16:39 ` sbaugh
2024-03-02 17:02 ` Eli Zaretskii
2024-03-02 20:33 ` Spencer Baugh
2024-03-03 6:13 ` Eli Zaretskii
2024-03-03 13:19 ` sbaugh
2024-03-03 15:42 ` Dmitry Gutov
2024-03-03 15:51 ` Eli Zaretskii
2024-03-01 19:30 ` tomas
2024-03-01 23:53 ` Dmitry Gutov
2024-03-02 5:57 ` tomas
2024-03-02 15:35 ` Dmitry Gutov
2024-03-02 16:31 ` tomas
2024-03-02 21:41 ` sbaugh
2024-03-03 6:25 ` tomas
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=ierzfvhspcq.fsf@janestreet.com \
--to=sbaugh@janestreet.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.