Vert interesting. How does this compare to the system that WindowsXP uses?

_________________
Sam

Hmmmm technical /Homer

Sounds good... can't wait for final release. Keep up the good work Hyperion...

_________________
A600 OS3.1 ACA620 | '030 A1200 OS3.5 | µA1-C 750GX OS4.1 | SAM460 OS4.1 | '040 A3000 OS2.1 | Christian Aid |

Very interesting! Thanks guys!

_________________
God is a man with a grey beard. His name is Jay Glenn Miner.

Interesting and a good read. I like that the website assumes some technical knowledge of the reader instead of just doing a mindless sales pitch. Looks professional and clean.
Who is writing this stuff anyhow? I'm sure the programmers supply the hard facts, but are they typing down the final touch too? Homever it is, is doing a good job - the text (and the website in general) have got a very nice blend of no-nonsense tech-info and juicy sales arguments.

I'm certainly no expert of memory systems, but I think I got the main idea of it at least.
.
SlimJim

Nice article, it's not too long or complicated. Small spelling error in the first picture though, fraGmentation, it's a fairly large text so it shows more than if it had been in the article...

_________________
AMiGA

REALLY COOL!

Does the memory fragmentation diagram on page 1 of the article remind anyone else of the robot control mini-game in Paradroid?

Very interesting article, too...

Michael.

Quote:

Who is writing this stuff anyhow?

This one was written by me, and then proof-read, clarified and largely re-written by two well-known Amiga writers, Richard Drummond and Andrew Korn

_________________
Thomas, the kernel guy

"I don't have a frigging clue. I'm norwegian" -- Ole-Egil

All opinions expressed are my own and do not necessarily represent those of Hyperion Entertainment

Cool. CUAmiga still lives...

Very fast typo editing too! - framentation!

_________________
Sam

Nice article! ..and to think this is in OS4 is even better!

The object caching sounds interesting, it'll be good to get stuck into the new
autodocs.

Cheers,
Bean.

_________________
OS4.1 + SAM Flex
RIP my A1XE.. that used to have an appetite for batteries!

Nice

_________________
"Miracles we do at once, the impossible takes a little longer" - AJS on Hyperion
Avatar is Tabitha by Eric W Schwartz

@EntilZha

How does the memory-system of OS4 compare to that of Windows/Linux/Mac OSX?

Is this the most 'modern' way of memory handling?

P.S. it is indeed great to hear that some of the ex- CU-Amiga staff is still involved in the Amiga scene; I really liked their magazine..

_________________
Quote:

You ain't seen me....right?

@EntilZha &
Richard and Andrew

The article was excellent. So was the layout and the diagrams.
As always, the display was especially considerate when using Amiga browsers.
I am proud to associate with such -fine- work.

Best Wishes,
#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

A pint for Hyperion & Co.

_________________
ikir

Wery interesting indeed.

A nicely written article. Thanks!

One thing though:
A couple of words (something like "the way") should be added to the first sentence.

Right now it is:
Quote:

Back in the old days of the original AmigaOS, the system used to allocate areas of unused memory to new tasks was pretty simple.

It should read something like:
Quote:

Back in the old days of the original AmigaOS, the way the system used to allocate areas of unused memory to new tasks was pretty simple.

Edit:
Actually it is fine in its original form. The thing that was throwing me off was taking the word "system" as referring to "AmigaOS;" but "system" in this sentence means "method." So all is good. Sorry for the unwarranted criticism.

Last edited by PEB on 14-Dec-2005 at 12:37 AM.

@Anomaly:

Quote:

Does the memory fragmentation diagram on page 1 of the article remind anyone else of the robot control mini-game in Paradroid?

It didn't at the time I read the article, but now, yes! That was a really unique game, I loved the music and sfx.. That robot control part almost always ended with my droid exploding though :(

Interesting article - well written and illustrated... but it raises some questions (naturally!)

1) Slab architecture was onbviously developed by Sun (see the references) - do they hold a patent on its use?

2) What other systems use this architecture? It appears to have been around since 1994 (in theory at least!) - if it hasn't been used, then is there a valid reason why not?

3) Could we have an illustration/example showing how the slab allocation process would deal with the fragmentation problem from the first set of examples (i.e. so we can compare what went wrong with the previous model, and how this has been resolved by this newer method)?

4) Does the implementation of this (radically different) memory allocation process break backwards compatibility, or is there a wrapper of some sort that mediates between the two methods? (Note however that I don't really give two hoots about full backwards compatibility - the quality of modern emulation is more than satisfactory!)

5) Is there an upper limit on the amount of memory that this architecture will support?

6) The process of caching object "hot spots" sounds interesting - is this something that a developer has to specifically expose to the memory API, or is it automatically and dynamically handled during run-time?

7) Do you actually have an operational version of your code which runs on multiple CPUs (and therefore *know* that it scales up in a linear manner) or is this something taken from the second reference (as indicated in the article) and is being borne in mind for the future...?

Apologies if any of these are covered in the references - it's a bit late to be delving into depp techincal documents, but if they answer any of my questions then I'd be more than happy to spend some time digging around myself... perhaps earlier in the evening!

Many many many thanks in advance to anyone who can clear these up for me!

_________________

well done guys.. but it will use AllocVec or AllocVecNew or what??
it is a joke..

Anonymous..

_________________
http://www.amigasoft.net

Quote:

2) What other systems use this architecture?

Eg. Linux

Last edited by miksuh on 13-Dec-2005 at 11:38 PM.
Last edited by miksuh on 13-Dec-2005 at 11:37 PM.