Syscalls versus Call Gates
Re: Syscalls versus Call Gates
Thread necro of the year (so far) award
Re: Syscalls versus Call Gates
For software isolation, surely array accesses would have to be bounds-checked? Static analysis can only go so far. Wouldn't the time spent bounds checking be far greater than any time saved from the MMU, address space switching, privilege level switching, TLB invalidating and the other reasons mentioned above?
Marionette the flexible kernel
- Colonel Kernel
- Member
- Posts: 1437
- Joined: Tue Oct 17, 2006 6:06 pm
- Location: Vancouver, BC, Canada
- Contact:
Re: Syscalls versus Call Gates
Read section 4.4 of this paper.
In a nutshell, run-time checks add about 4.5% overhead, but for many types of real-world tasks this will be outweighed by the cost of ring transitions, TLB misses, etc.
In a nutshell, run-time checks add about 4.5% overhead, but for many types of real-world tasks this will be outweighed by the cost of ring transitions, TLB misses, etc.
Top three reasons why my OS project died:
- Too much overtime at work
- Got married
- My brain got stuck in an infinite loop while trying to design the memory manager
Re: Syscalls versus Call Gates
Thank you for the link to the paper, Colonel. I tried downloading various papers from Microsoft's website, but the server just wasn't working. I wonder what server software they're running
Marionette the flexible kernel