From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Subject: Re: GUILE GC -- Write barrier for vectors
Date: Tue, 16 Jul 2002 11:22:41 +0200 [thread overview]
Message-ID: <15667.58849.671382.883437@meddo.cs.uu.nl> (raw)
In-Reply-To: <15667.21636.174313.24740@blauw.xs4all.nl>
hanwen@cs.uu.nl writes:
> I'm reading the patent (gosh, what verbosity) -- but interestingly,
> the claim is only made for not copying entire pages (cards in Scheme
> terms), that are marked conservatively. If you one uses a second set
> of mark bits, you could leave alone exactly those objects that are
> marked conservatively (iso. the whole page). The price is that you
> have another mark-bit vector (1.5 % memory overhead), that the free
> space in the conservatively marked pages is fragmented, and that there
> is more overhead (checking the marked-conservatively-bit) during the
> copy phase.
Actually, I can top that. If you store the range of cells that is
marked conservatively, you can still beat the patent but avoid the 2nd
bitvector overhead. All this (bitvector ptr, conservative-cell range,
generation count and card) flags could even be stored in the 1st
header cell.
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-16 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 22:14 GUILE GC -- Write barrier for vectors hanwen
2002-07-15 10:56 ` Miroslav Silovic
2002-07-15 11:00 ` Han-Wen Nienhuys
2002-07-15 11:36 ` Miroslav Silovic
2002-07-15 16:49 ` Dirk Herrmann
2002-07-15 18:22 ` Han-Wen Nienhuys
2002-07-15 20:07 ` Dirk Herrmann
2002-07-15 23:02 ` Han-Wen
2002-07-16 9:22 ` Han-Wen Nienhuys [this message]
2002-07-16 23:04 ` Dirk Herrmann
2002-07-16 23:26 ` Han-Wen
2002-07-17 21:53 ` Han-Wen
2002-07-19 23:48 ` Dirk Herrmann
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=15667.58849.671382.883437@meddo.cs.uu.nl \
--to=hanwen@cs.uu.nl \
/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).