|
![](/i/fill.gif) |
On 8/12/2012 2:23, Orchid Win7 v1 wrote:
> I like how the algorithm description is sufficiently vague that you can't
> tell how it actually works.
It was four clicks away, with the previous three clicks giving successively
more detailed descriptions.
http://labs.oracle.com/jtech/pubs/04-g1-paper-ismm.pdf
You're welcome.
> it "detects" any attempt to access a moved object, but again doesn't say
> how.
Memory mapping. It traps on reading the memory that hasn't been fixed yet,
then fixed up the entire page worth of references, then marks the memory as
readable.
> Since it's impossible to have a machine with 140GB of RAM,
Since when is it impossible? We had 128G of RAM on the Sparcstation we used
back in 1995 or so. And that wasn't even a mainframe.
--
Darren New, San Diego CA, USA (PST)
"Oh no! We're out of code juice!"
"Don't panic. There's beans and filters
in the cabinet."
Post a reply to this message
|
![](/i/fill.gif) |