And perhaps we should also mention one of the main reasons: A system call for each single memory allocation will lead to a noticably slow system.Rew wrote:Pear, are you trying to use a system call for object allocation? While it can work, there is a different way of organizing allocation that most people use.
Syscalls benefits and issues?
Re: Syscalls benefits and issues?
Re: Syscalls benefits and issues?
At the moment no I am not. I actually don't have any syscalls. I went another route and was able to get Programs working just fine, they can access any Kernel, and Os call as long as its visible to the program, but because its not a syscall the speed and performance is quite impressive. Nice thing is, I can change my Os and add onto it without corrupting the Program, so basically I have backwards compatibility as well as forward compatibility.Kevin wrote:And perhaps we should also mention one of the main reasons: A system call for each single memory allocation will lead to a noticably slow system.Rew wrote:Pear, are you trying to use a system call for object allocation? While it can work, there is a different way of organizing allocation that most people use.
- Matt
Re: Syscalls benefits and issues?
They did. It's called Singularity.Rew wrote:On another note, I wonder why microsoft hasn't done this... it would give .NET a massive performance boost in windows for quite a few applications.