To view parent comment, click here.
To read all comments associated with this story, please click here.
AmigaOS is a Single Address Space OS, where an App or OS can pick any object of other applications. That makes data passing and sharing easy and fast. As I see it, the only way to do memory protection transparently is protection domains that require tagged memory allocations to specify data access rights.
viton,
"AmigaOS is a Single Address Space OS, where an App or OS can pick any object of other applications. That makes data passing and sharing easy and fast."
Oh I see, thanks for the answer So it's about shared objects... Well I guess at least it's a good technical reason for not having protection.
You can still emulate a single address space, with memory protection.
I can understand that adds some complexity to the OS design. But then the problem is then code complexity, not performance overhead from memory protection (which is practically a non-issue in most modern architectures).
But then it is not my project. So whatever it is they want to do, it is their pregogative.
Edited 2011-10-19 19:11 UTC





Member since:
2011-01-28
ncafferkey,
"No, memory protection hurting performance isn't a big worry among AROS devs or users. The real issue is finding a way to introduce it without breaking source compatibility (too much)."
I know very little about this platform, but I'm curious what kind of software requires the absence of memory protection? Is this because amiga apps routinely access hardware directly? Or they routinely read/write bios/os structures?