From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Pip Cet <pipcet@gmail.com>
Cc: rudalics@gmx.at, Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Opportunistic GC
Date: Mon, 08 Mar 2021 10:46:25 -0500 [thread overview]
Message-ID: <jwv35x57iw7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAOqdjBfhV2GLw5ANO_oRd6vBmN9U+rPzUZ8x6s5b9obWMdJUhA@mail.gmail.com> (Pip Cet's message of "Mon, 8 Mar 2021 15:02:18 +0000")
>> Ah, so not really an easy change after all.
>
> For conses, it's easy. Instead of keeping the mark bits in the cons
> block, we keep a pointer to the mark bits in the cons block, and
> allocate the mark bits separately and (hopefully) on a different page.
What you mean is that it's easy because the markbits are already
separate from the cons objects (same for floats). We could also just
increase the size of the cons blocks such that their markbits area takes
up a whole page. That means cons blocks of about (* 16B/cons 8b/B) =>
128 pages => 512KB.
>> And how do you propose to keep the mark bits separately and still
>> maintain coherency between the object and its bits?
> Just as we do for pdumper, which already does this. In fact, I'm
> pretty sure it was Daniel who said a while ago that he wants to extend
> that to all GCable objects, not just those that live in the pdmp.
Yes, it's a good idea to do that in general.
Stefan
next prev parent reply other threads:[~2021-03-08 15:46 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 [this message]
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.
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=jwv35x57iw7.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=pipcet@gmail.com \
--cc=rudalics@gmx.at \
/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).