unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Stefan Israelsson Tampe <stefan.tampe@spray.se>
To: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: postpone discussion.
Date: Sat, 28 Aug 2010 23:21:53 +0200	[thread overview]
Message-ID: <201008282321.53796.stefan.tampe@spray.se> (raw)
In-Reply-To: <m3y6bq3az5.fsf@unquote.localdomain>

On Saturday, August 28, 2010 07:26:06 pm you wrote:
> On Sun 15 Aug 2010 06:26, Stefan Israelsson Tampe <stefan.tampe@spray.se> 
writes:
> > Probably for some interesting applications there will be a hughe
> > demand on memory. And Keeping the redo tree slim can have a great cost
> > benefit. I believe it is possible to save like 4x in space. And
> > certaily 2x if guile was on a 32bit. Now it might be interesting to
> > have guile in 64bit, but let guile sit on a 32 bit adress
> > subspace. And only let the redo tree take advantage of adressing more
> > then 32bits. This would logically save 2x of memory space. So is it
> > possible to accomplish this?
> 
> Well, if you want a 32-bit address space... just compile a 32-bit
> version, right?

Well here is a case where you may want one huge user datastructure that 
can cover many gigabytes - so you would like to have 64bit to adress 
this creature. So see the pattern here. One blob in 
the c-code custom space that is huge and all guile sitting on a small iland
that could have been 32 bit. So one should be able to compress.

Mayby I'm ignorant on the meaning of compiling to 32bit though.

> > Hope this was stimulating.
> 
> It was interesting. I did not understand it all but am happy to listen
> 
> :)

:-)

> Andy

Stefan



      reply	other threads:[~2010-08-28 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 13:26 postpone discussion Stefan Israelsson Tampe
2010-08-28 17:26 ` Andy Wingo
2010-08-28 21:21   ` Stefan Israelsson Tampe [this message]

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=201008282321.53796.stefan.tampe@spray.se \
    --to=stefan.tampe@spray.se \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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).