From: Michael Livshin <guile@cmm.kakpryg.net>
Subject: Re: lazy sweeping.
Date: Mon, 29 Jul 2002 16:00:08 +0300 [thread overview]
Message-ID: <s3sn22lmef.fsf@cmm.kakpryg.net.cmm> (raw)
In-Reply-To: 15685.14250.901905.318924@meddo.cs.uu.nl
Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
> guile@cmm.kakpryg.net writes:
>> if I remember correctly, Guile has some logic to cope with suddenly
>> running out of file descriptors: it calls GC in the hope that some
>> port objects are unreachable.
>>
>> I guess now you don't have to nesessarily do a full GC right away,
>> instead you may want to finish the sweep first and see if that helps,
>> and only do a new GC if finishing the sweep haven't helped. hmm. so
>> that's not as fiddly as I thought, and probably works as it is.
>>
>> ditto for malloced memory, I guess.
>
> Hrm. I'll have to add some more logic then -- we want to be able to
> completely clean the heap, but not advance the "free mem starts here"
> pointer. What would be the right behavior: doing a full sweep, or a
> mark + full sweep? Or maybe just both (first the full sweep, if it
> doesn't yield enough: the full mark.)
that's what I've meant, yes. however, it's just as optimization, and
the occurences where it might theoretically matter (system heap
exhaustion or running out of file descriptors) could probably be
considered to be rare enough.
as long as you take care to finish the last sweep before marking, you
should be fine, correctness-wise.
--
REALITY is an illusion that stays put.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-29 13:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 23:32 lazy sweeping Han-Wen
2002-07-29 0:07 ` Michael Livshin
2002-07-29 9:48 ` Han-Wen Nienhuys
2002-07-29 10:14 ` Michael Livshin
2002-07-29 12:40 ` Han-Wen Nienhuys
2002-07-29 13:00 ` Michael Livshin [this message]
2002-07-29 13:06 ` Han-Wen Nienhuys
2002-07-30 10:09 ` Han-Wen
2002-07-30 12:10 ` Michael Livshin
2002-07-29 4:31 ` Tom Lord
2002-07-29 15:17 ` Han-Wen Nienhuys
2002-07-29 13:16 ` Mikael Djurfeldt
2002-07-29 13:22 ` Han-Wen Nienhuys
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=s3sn22lmef.fsf@cmm.kakpryg.net.cmm \
--to=guile@cmm.kakpryg.net \
/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).