the efficency requires something like a bridge. The idea is very nice, but you have a missing mind.
The CPU haves to organize the memory-fields, their sizes and functionals.
The GPU gots the delegations from CPU, but if you all pack into the memory, its a great mistake.
Please remember, what's the difference between Pascal and C! What happens, when you're overloading the memory? If you have no restriction rules, you will lose control. Pascal expects to know, what happens and whats to do with happy data. C expects nothing to work, what happens are high riskly and creapy data.
So i'll suggest, to secure the risk of C with a fence from Pascal. Then you should be run on fastest stability. The fency tables could be pushed to the regular RAM. Every part will haves their autonomous area. It's like a ping-pong if used direct pointing and direct adressing same time.
We had our own projects in GDR. And the fight between the Pascal-hardliners and the C-riskers were a hard one. I remember to a conversation of our homeland-security in the mid of eightees. Through the way of disassembling and reversing to C we found a long list of bugs, that we fixed.
It not means, that the coders of IBM made ugly work! But the side-effects they did'nt see directly.
But thats the reason, why all the virtualization concepts are compromitted by design.
Apple and Microsoft could not fix it and are kicked off. No more kidding patches please!
Linux can be fixed, if Linus comes out of his angrybird box.
Maybe, that some popular emulators are kicked off too, but you know, whats needed.
Hey BeRo,
the efficency requires something like a bridge. The idea is very nice, but you have a missing mind.
The CPU haves to organize the memory-fields, their sizes and functionals. The GPU gots the delegations from CPU, but if you all pack into the memory, its a great mistake.
Please remember, what's the difference between Pascal and C! What happens, when you're overloading the memory? If you have no restriction rules, you will lose control. Pascal expects to know, what happens and whats to do with happy data. C expects nothing to work, what happens are high riskly and creapy data.
So i'll suggest, to secure the risk of C with a fence from Pascal. Then you should be run on fastest stability. The fency tables could be pushed to the regular RAM. Every part will haves their autonomous area. It's like a ping-pong if used direct pointing and direct adressing same time.
We had our own projects in GDR. And the fight between the Pascal-hardliners and the C-riskers were a hard one. I remember to a conversation of our homeland-security in the mid of eightees. Through the way of disassembling and reversing to C we found a long list of bugs, that we fixed. It not means, that the coders of IBM made ugly work! But the side-effects they did'nt see directly.
But thats the reason, why all the virtualization concepts are compromitted by design.
Apple and Microsoft could not fix it and are kicked off. No more kidding patches please!
Linux can be fixed, if Linus comes out of his angrybird box. Maybe, that some popular emulators are kicked off too, but you know, whats needed.