From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: Pip Cet <pipcet@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Eli Zaretskii <eliz@gnu.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Opportunistic GC
Date: Mon, 08 Mar 2021 16:18:45 +0000 [thread overview]
Message-ID: <xjfwnuhwrdm.fsf@sdf.org> (raw)
In-Reply-To: <CAArVCkQA2b-DigPJ4ZfMpETr+tRRAjLF4kNMGxSyOa7wLofF_w@mail.gmail.com> (Philipp Stephani's message of "Mon, 8 Mar 2021 17:14:51 +0100")
Philipp Stephani <p.stephani2@gmail.com> writes:
[...]
>> I also expect fork will work, I'm more wondering about interaction with
>> sockets file descriptors or anything else in our codebase and/or in
>> libraries we have loaded.
>>
>> I've read in the past this is an issue in practice in non trivial code
>> and that, because the typical use of fork () nowadays is just to run
>> afterward exec (), operating in the grey between the two was not really
>> a good idea. But I don't have the reference now and if you say it works
>> I've no reasons not to trust you.
>
> The restriction is that you can only call async-signal-safe functions
> in subprocesses before exec. See e.g. the man page for fork on
> GNU/Linux.
Can we enforce that for our case?
Andrea
next prev parent reply other threads:[~2021-03-08 16:18 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 3:35 Opportunistic GC Stefan Monnier
2021-03-08 7:20 ` Pip Cet
2021-03-08 8:26 ` martin rudalics
2021-03-08 9:02 ` Pip Cet
2021-03-08 9:51 ` martin rudalics
2021-03-08 10:44 ` Pip Cet
2021-03-08 11:37 ` martin rudalics
2021-03-08 12:27 ` Pip Cet
2021-03-08 18:06 ` martin rudalics
2021-03-08 18:24 ` Concurrent GC via fork (was: Opportunistic GC) Stefan Monnier
2021-03-09 8:10 ` Concurrent GC via fork martin rudalics
2021-03-10 20:35 ` Opportunistic GC Pip Cet
2021-03-08 11:38 ` Stefan Kangas
2021-03-08 12:55 ` Pip Cet
2021-03-08 14:06 ` Andrea Corallo via Emacs development discussions.
2021-03-08 14:49 ` Eli Zaretskii
2021-03-08 15:02 ` Pip Cet
2021-03-08 15:23 ` Eli Zaretskii
2021-03-08 15:39 ` Pip Cet
2021-03-08 16:27 ` Eli Zaretskii
2021-03-08 16:35 ` Pip Cet
2021-03-08 17:06 ` Eli Zaretskii
2021-03-08 15:46 ` Stefan Monnier
2021-03-08 16:11 ` Pip Cet
2021-03-08 16:37 ` Stefan Monnier
2021-03-08 14:01 ` Andrea Corallo via Emacs development discussions.
2021-03-08 15:04 ` Pip Cet
2021-03-08 15:50 ` Stefan Monnier
2021-03-08 15:52 ` Andrea Corallo via Emacs development discussions.
2021-03-08 16:14 ` Philipp Stephani
2021-03-08 16:18 ` Andrea Corallo via Emacs development discussions. [this message]
2021-03-08 16:40 ` Philipp Stephani
2021-03-08 16:44 ` Stefan Monnier
2021-03-08 17:13 ` Eli Zaretskii
2021-03-10 20:25 ` Pip Cet
2021-03-10 20:48 ` Eli Zaretskii
2021-03-11 7:55 ` Pip Cet
2021-03-11 8:37 ` Eli Zaretskii
2021-03-11 9:03 ` Pip Cet
2021-03-11 9:34 ` Eli Zaretskii
2021-03-11 10:11 ` Pip Cet
2021-03-11 11:35 ` Eli Zaretskii
2021-03-09 6:22 ` Richard Stallman
2021-03-09 8:11 ` Pip Cet
2021-03-10 5:52 ` Richard Stallman
2021-03-08 14:45 ` Eli Zaretskii
2021-03-08 14:57 ` Pip Cet
2021-03-08 15:16 ` Eli Zaretskii
2021-03-09 13:01 ` Eli Zaretskii
2021-03-10 20:21 ` Pip Cet
2021-03-10 20:41 ` Eli Zaretskii
2021-03-11 8:06 ` Pip Cet
2021-03-11 9:03 ` Eli Zaretskii
2021-03-08 16:03 ` Concurrent GC via `fork` (was: Opportunistic GC) Stefan Monnier
2021-03-08 16:25 ` Pip Cet
2021-03-08 17:37 ` Concurrent GC via `fork` Stefan Monnier
2021-03-08 19:21 ` Lars Ingebrigtsen
2021-03-10 17:18 ` Opportunistic GC Matt Armstrong
2021-03-10 19:38 ` Pip Cet
2022-07-05 1:47 ` Stefan Monnier
2022-07-05 13:49 ` T.V Raman
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=xjfwnuhwrdm.fsf@sdf.org \
--to=emacs-devel@gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=p.stephani2@gmail.com \
--cc=pipcet@gmail.com \
/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).