From: Andi Kleen <ak@suse.de>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Speeding up GC
Date: Tue, 04 Jun 2002 03:52:00 -0000 [thread overview]
Message-ID: <p73n0ubcold.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Richard Henderson's message of "4 Jun 2002 03:06:09 +0200"
Richard Henderson <rth@redhat.com> writes:
> A better way to do this is to actually compact the GC arena
> and mark the pages read-only. If the objects are modified,
> the SIGSEGV handler marks the page read-write again and flags
> the page as having been modified.
Unfortunately changing pages to read only and back is rather expensive.
Cheaper would be to expose the hardware's page dirty bit to user space
and use it for this. Apparently some OS like Solaris support it already
(at least that is what the relevant function in the boehm-gc suggest)
I guess it could be added to Linux too.
-Andi
next parent reply other threads:[~2002-06-04 10:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <j47klg8pfy.fsf@informatik.hu-berlin.de.suse.lists.egcs>
[not found] ` <20020603180553.A13829@redhat.com.suse.lists.egcs>
2002-06-04 3:52 ` Andi Kleen [this message]
2002-06-04 6:57 ` John Levon
2002-06-04 7:14 ` Paul Koning
2002-06-04 7:37 ` David S. Miller
2002-06-04 7:51 ` Daniel Berlin
2002-06-04 7:53 ` David S. Miller
2002-06-04 7:58 ` Andi Kleen
2002-06-04 8:08 ` David S. Miller
2002-06-04 8:55 ` law
2002-06-04 8:17 ` Marc Espie
2002-06-04 9:21 ` Joe Buck
2002-06-04 8:10 ` Marc Espie
2002-06-04 8:58 ` David S. Miller
2002-06-04 9:05 ` Marc Espie
2002-06-04 9:35 ` David S. Miller
2002-06-04 8:43 ` law
2002-06-04 8:59 ` David S. Miller
2002-06-04 10:15 ` Richard Henderson
2002-06-04 10:22 ` David S. Miller
2002-08-17 5:13 Tim Josling
2002-08-18 0:25 ` Guillermo Ballester Valor
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 4:56 Robert Dewar
2002-06-03 6:25 Martin v. Löwis
2002-06-03 6:39 ` David S. Miller
2002-06-03 18:10 ` Richard Henderson
2002-06-04 2:34 ` Marc Espie
2002-06-04 3:15 ` David S. Miller
2002-06-04 11:42 ` Alexandre Oliva
2002-06-04 12:10 ` Richard Henderson
2002-06-04 12:39 ` David S. Miller
2002-06-04 12:38 ` David S. Miller
2002-06-04 10:03 ` Richard Henderson
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=p73n0ubcold.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.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.
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).