Welcome, Guest. Please login or register.

Author Topic: Memory Management in AmigaOS4.0 Explained  (Read 11332 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Tigger

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 1890
    • Show only replies by Tigger
Re: Memory Management in AmigaOS4.0 Explained
« Reply #44 from previous page: December 15, 2005, 05:00:51 PM »
Quote

Okay, so you are say that Amiga OS 4.0 is the only current OS that is using this nearly 40 year old idea?

No, in fact if you were reading the thread you'd see I pointed out that most OS's use this method.

Quote

So, that would make Window one of the only true modern cutting edge inovative OSs!

Well it uses Slab too, so using Hyperion logic, apparently it is cutting edge and super innovative, of course it and I believe all of the others that actually use it, were designed to use it from the start, not trying to shoehorn it in ala what Hyperion is trying to do with AmigaOS.
    -Tig
Well you know I am scottish, so I like sheep alot.
     -Fleecy Moss, Gateway 2000 show
 

Offline Hattig

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 901
    • Show only replies by Hattig
Re: Memory Management in AmigaOS4.0 Explained
« Reply #45 on: December 15, 2005, 05:40:31 PM »
In the end the point is that Amiga OS 4.0 now has memory allocation algorithms that aren't {bleep}, and are comparable to what is used in other operating systems today.

What part of this is bad? Would you rather they had left it as it was?

For people who don't care about AmigaOS4 I wonder why you seem to care so much. I think you do it to troll, you're not adding anything to the discussion, you appear to have a personal vendetta against the Hyperion people, people that have at least put a lot of their time and money into a platform that you claim to love. Indeed you ignore technical responses that don't suit you, and nitpick on people's words. Grow up.
 

Offline Tigger

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 1890
    • Show only replies by Tigger
Re: Memory Management in AmigaOS4.0 Explained
« Reply #46 on: December 15, 2005, 06:19:18 PM »
Quote

What part of this is bad? Would you rather they had left it as it was?


They took a working system with known inefficiencies and have replaced it with another system with different inefficiencies and potential issues running current software.  Is that really better then fixing the real issues with the OS so it can be done.

Quote

For people who don't care about AmigaOS4 I wonder why you seem to care so much.

I and a couple of hundred other developers paid for a copy in OS4 over 3 years ago, it would be really nice to actually see the OS get completed.

Quote

I think you do it to troll, you're not adding anything to the discussion, you appear to have a personal vendetta against the Hyperion people, people that have at least put a lot of their time and money into a platform that you claim to love.

So now its trolling to point technical problems with what people post on there website??  The only Hyperion person I dont like is the Belgian midget, and thats just because he told everyone he was going to kick my ass at Amiwest, till I actually showed up and he realized that Lee as the little guy of the Huntsville Mafia could break him into pieces and me I wouldnt even break a sweat doing it.  

Quote

Indeed you ignore technical responses that don't suit you, and nitpick on people's words. Grow up.

I havent ignored any technical responses.  In fact the only real technical response to me has been Rich, and Rich agrees that Hyperion example is poor to say the least.  The rest of Richs description is basically correct, his comment is that slab memory overhead could be less then of the current system (actually I think hes arguing that they are equal), traditionally slab memory overhead is usually larger then that of the amiga system, and if they actually have less memory overhead then on the current system, wouldnt that, not the poor example that slab doesnt help with be on the site??  Now why dont you grow up, and if you really dont like the thread, dont read it, or post in it.
    -Tig
Well you know I am scottish, so I like sheep alot.
     -Fleecy Moss, Gateway 2000 show
 

Offline Hattig

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 901
    • Show only replies by Hattig
Re: Memory Management in AmigaOS4.0 Explained
« Reply #47 on: December 15, 2005, 07:11:08 PM »
Now why dont you grow up, and if you really dont like the thread, dont read it, or post in it.

I like the subject of the thread, so why shouldn't I post in it?

My point was that people are making too much effort in deriding it, beyond simple academic interest. For some it is 'it's AmigaOS, so let's find an issue with whatever it is and then harp on about it for ever and ever'.

Even I agree the example was poor, but a poor example does not negate the fact that this replacement method is most likely a hell of a lot better than the old method. And better is good. It isn't as if people haven't been running AmigaOS4 beta for a long time anyway. There must be a good reason that many other operating systems use the same or a similar allocation algorithm - probably the usage situation is a lot different these days, and a list based mechanism will be a lot slower with hundreds/thousands of entries, whereas the slab system, whilst taking a little more memory, will be a lot faster?

Was the Belgian guy Ben Hermans? He did go on a bit on ANN in the day, a bit too far. Wasn't he let go from Hyperion?

I'm sorry you lost your money on the Amiga Inc coupon thing (I presume). Note that whilst being interested in AmigaOS4 I don't have an interest in Amiga Inc themselves, whatever they're doing these days. They messed around the community too much.
 

Offline Tigger

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 1890
    • Show only replies by Tigger
Re: Memory Management in AmigaOS4.0 Explained
« Reply #48 on: December 15, 2005, 09:01:31 PM »
Quote

this replacement method is most likely a hell of a lot better than the old method. And better is good. It isn't as if people haven't been running AmigaOS4 beta for a long time anyway.


First of all, I'm not sure that this is actually in the Beta, secondly, where I think this is most likely to break things is JIT, which of course isnt in the version being used by most of the people.  

Quote

There must be a good reason that many other operating systems use the same or a similar allocation algorithm

A couple of reasons, but they dont have (to quote Bernie) our one big hunk of memory design, and you might note all of them support multi-processor (which is why I've used a derivation of it in our stuff in the past).   So amigaos doesnt have the reason to use it that others do, and again changing the memory allocation system would have been way down on my list of things to do to upgrade OS4.

Quote

Was the Belgian guy Ben Hermans?

Absolutely.  

Quote

I'm sorry you lost your money on the Amiga Inc coupon thing (I presume)


Actually it was what I like to call the pre-coupon scam.  They sold 1000 copies of AmigaDE Partypack, which was to include a free OS4 for $100 to a bunch of developers.  The product was fairly useless, and its now actually 4 years later (that was actually 2001) and we still dont have an OS4.  Of course being one of those that sat through fleecys developer seminar/beastiality conference in 2000, I'm not sure why I expected more from them.    
    -Tig
Well you know I am scottish, so I like sheep alot.
     -Fleecy Moss, Gateway 2000 show
 

Offline Rob

Re: Memory Management in AmigaOS4.0 Explained
« Reply #49 on: December 15, 2005, 10:42:17 PM »
>First of all, I'm not sure that this is actually >in the Beta, secondly, where I think this is >most likely to break things is JIT, which of >course isnt in the version being used by most of >the people.

I think one of the Friedens stated somewhere that it does not break compatability with software.  I understand the old allocation methods still work (excuse my lack of technical knowledge).

Also with OS4's JIT engine, software known to have problems with the JIT are put on a black list which can be ammended. IIRC When a black listed program is run it is referred to the interpretive 68k emulator.  
Therefore programmes that work now should still work when the final version arrives.