Yes, Ami603. I see it now. You're right. My mistake....

_________________
Helge K. Leaving the Amiga in favour of a PC..

Well, everybody. There was a long time since i was at school and i did have some algebra. Math was never my strenght, but rather a weakness to me. Sorry to disappoint you all...

_________________
Helge K. Leaving the Amiga in favour of a PC..

Quote:

Of course we should by now alredy know that there are no other specialists but Hyperion, and also that the world is black and white and... yada yada... :-p

Seems the first specialist is already here! Next.

_________________
Games, programs, reviews

I know that "virtual mem" does not mean swapping per se, but so doesn't "memory mapped files". However, the articel mentioned swapping beeing available at some point (which I think is a good thing - especially if you have some kind of control over it).

A memory mapped file would be just another "plugin" which would work simialr to a swaped memory, except, that, e.g. the app would customize a file on disk and "declare" it as memory. What you can do then is, instead of loading data from it, you simply "memcpy" from there and the DOS/mem system takes care of the rest (more like a swapped memory). This has various benefits over a file system in the way, you do not need to collect a ton of files, but have one big chunk and it is transparent to the memory and therefore less complicated to use then e.g. file I/O.

_________________
AmigaOne XE G3/933/VIA/FM801/R200 (fixed),
G3SE/600/Voodoo3/Sil680/RTL8139/SBLive! (noiseless!)
µA1-MK2/G3/933/R200/CMI8738
XE/G4 (broken 7450/800)

With the time and new techniques Windows becomes slower and bigger and AmigaOS becomes faster and more compact AmigaOS is like good wines, with the time becomes better and Windows is like bad wines, with the time becomes vinegar

_________________
No PowerPC, No Fun
Make Amiga Great Again

@Rogue

Thanks for the continuing effort
AND
for letting us know about it!

_________________

Very interesting read. I hope they are not giving up any trade secretes, is this type of memory management unique to OS4 on the Amiga?

Nice to have some good news. I think the swap part is going to be gathering dust most of the time, unless you start working with multimedia files(Mpgs and such).

So when do we mortals get to try it out? I know, when it's done!

Nice to see the progress. Keep up the great work, can't say enough!

Quote:

dos.library allowing you to "allocate" a mem image from disk ?) That would be great.

That would be a sure way to fill up the address space, since AmigaOS has only one, shared by all tasks. And if we're talking about little files, then you'd not have any advantage over simply loading them to memory, and the effect would be the same.

_________________
“It is well enough that people of the nation do not understand our banking and monetary
system, for if they did, I believe there would be a revolution before tomorrow morning.”
~~ Henry Ford

Quote:

That would be a sure way to fill up the address space, since AmigaOS has only one, shared by all tasks. And if we're talking about little files, then you'd not have any advantage over simply loading them to memory, and the effect would be the same.

First, this is not new and other OSs can handle that. And second, one could simply free that mem again after usage. "Filling up 4GB" would mean multiple apps doing that thing at the same time, not releasing the mem again, which I doubt will happen.

Also, it would be an _additional_ feature (ever heard about a .pak file?). Nobody forces anyone to use it (and I understand the same would apply for swap space - as long as you can switch that off).

About the speed concerns and virtual mem space. AFAIK the current implementation does that already, but the allocator has been changed. One question isn't answered, though. Is the PUBMEM block now gone ? I think so, isn't it ?

_________________
AmigaOne XE G3/933/VIA/FM801/R200 (fixed),
G3SE/600/Voodoo3/Sil680/RTL8139/SBLive! (noiseless!)
µA1-MK2/G3/933/R200/CMI8738
XE/G4 (broken 7450/800)

Quote:

First, this is not new and other OSs can handle that.

Other OSs have multiple address spaces, that's how they can deal with it.

Quote:

And second, one could simply free that mem again after usage.

I think you're missing the point of mmap'ing a file.

Memory mapping a file is useful when you want to let the OS handle for you the buffering at the lowest possible level, while still being able to access the file as if it were loaded totally into memory. This is useful mostly for huge files, as little files can be loaded directly into memory without wasting too much time during the process. Loading a 1GB file into memory, on the other hand, would cost swap space and time.

A mmap'ed file is like a swap file created on demand.

Quote:

"Filling up 4GB" would mean multiple apps doing that thing at the same time, not releasing the mem again, which I doubt will happen.

No, it would mean mmap'ing a DVD ISO, for instance.

Quote:

Also, it would be an _additional_ feature (ever heard about a .pak file?). Nobody forces anyone to use it (and I understand the same would apply for swap space - as long as you can switch that off).

I just said that it wouldn't be useful, given the other limitations.

More useful would be a C++ class which let you access a file via an overloaded [] operator, mimicing a mmapped file, without the problems of a mmapped files.

_________________
“It is well enough that people of the nation do not understand our banking and monetary
system, for if they did, I believe there would be a revolution before tomorrow morning.”
~~ Henry Ford

@Hyperion and OS4 Devs

A BIG THANK YOU... now release an update 5 please

_________________
ikir

That's very interesting article.

Yeah!

Something happening!!!

_________________
retired

@falemagn

Multiple address space can be the next goal?

_________________
retired

It sounds neat but these memory articles almost always blow my mind. I hear a "whoosh" just above my head but that's all I get.

Still, nice one Hyperion et al.

FuZion.

That would require memory protection.

_________________

Quote:

Thank you for the well written and informative update.

Can't take credit for it, the article was written by Thomas ;)

_________________
Seriously, if you want to contact me do not bother sending me a PM here. Write me a mail

Quote:

Even more impressive is that it says when booting up Workbench with this new memory system, it should be using less than 2KB in all!!! That's pretty much awesome!

Uhm, no, at the time of workbench boot, there's already 40000 allocations of 2KB or less each...

_________________
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

Quote:

That would require memory protection.

Actually, no. It would require separate address spaces. It will mess up pretty badly when someone writes into another one's address space, but that is already the case now. It does in no way require memory protection.

_________________
Seriously, if you want to contact me do not bother sending me a PM here. Write me a mail

Like i said Enthza, math is my weakness...But you know these stuffs much better than i do..

_________________
Helge K. Leaving the Amiga in favour of a PC..