![]() Have a device to swap to, either locally on over a fast network. Virtual memory will only help with the problem of limited RAM if you Have a good reference for it handy, I didn't. Gemstone was something that I considered mentioning, but since I don't Summerschool/summer09/curriculum.html see David Bacon). Impression, that they do very similar stuff, to what I vaguely Thing, but the lecture I followed on the IBM Metronome GC gave me the Guess, that such a GC would allow the OS to swap out unused stuff toįrom the top of my head, I don't remember any GC which did such a Reads/writes into account when it moves objects in memory? I would Something like a generational GC which might also take the history of Should take more responsibilities and OS should be more like anĮxtended hypervisor, wouldn't it be a practical solution to have Looking for a garbage collector which is aware of paging/virtual Hm, am not entirely sure, but thats sounds much more like you are ![]() > ? why I should use 50 if maybe I just use 10 ? And what percentage of the image is really used > Why ? ok, that's not too much.but if you have several images > be VERY valuated in such devices, but probably also useful for a desktop ![]() > "standard" VM that can have a mechanism to act as Virtual Memory. > have a complete different VM neither image. I have your rss and I saw your paper the other day.it is in my toreads Ps: I know you are developing VMs also (or similar). Ok.that's just an idea.then, I don't know what of what will I do hahahahah BTW, this paper (altought is java) is very interesting: I would also like to be able to handle different kinds of memory. I want a VM still written in SLANG and not couple with any hardware in particular. Tightly coupled to the hardware of the Lego Mindstorms NXT robot.". And what percentage of the image is really used ? why I should use 50 if maybe I just use 10 ?Įven more, if you read their site "The NXTalk virtual machine is a Smalltalk VM written in pure C and Why ? ok, that's not too much.but if you have several images running.that can be a lot. This can be VERY valuated in such devices, but probably also useful for a desktop application. It would be cool to have a "standard" VM that can have a mechanism to act as Virtual Memory. However, my idea is not to have a complete different VM neither image. The numbers they achieved (memory used for example) is incredible. I attended ESUG last year, I saw their talk, and I really cannot believe what they have done. One of my first question to my thesis supervisor was "why we need this if we have NXTalk working and really well ?" "Objects live permanently in secondary memory and cycle into primary as they are needed in computation." “Primary memory is a cache for objects temporarily involved in computation." Something that stands the following two phrases (extracted form LOOM paper): I am interested in Virtual Memory scheme in general, not necessary LOOM. So, I think that a LOOM implementation nowadays, with same pointer sizes and modern GC, should be much simpler. I think we don't have this problem nowadays. Most of the problems and complexity of LOOM are due to this. The key point of LOOM is that it uses 16 bits addresses for primary memory (RAM) and 32 bits addresses for secondary memory (disk). Nowadays GCs take into account most of those problems, thus a lot of complexity should be reduced Most of the problems/solution it presents, were because of the limited GC techniques used by that time. I really like that paper and I want to know if there is some newer implementation. LOOM was a Virtual Memory scheme for Smalltalk-80. Hi and welcome!! Now that there are people registered, we can start to discuss :)ĭuring the last two weeks or so I have been reading and understanding (into the very deep details) the LOOM (Large Object Oriented Memory) paper that you can find here:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |