Re:This is the exploit equivalent of that guy who played the...
by lallysingh on Tuesday July 07, 2009 @08:40AM
(#691351)
Two things:
1) It's a memory allocation, scanning data structures, possibly involving some thread-locking or even a system call. A single check is cheap. If you want to keep the CPU happy the 99% of the time, put the most likely case first, so the CPU doesn't have to jump. Speculation should help mitigate the rest.
2) A good reason why operator new() throws by default.
1) It's a memory allocation, scanning data structures, possibly involving some thread-locking or even a system call. A single check is cheap. If you want to keep the CPU happy the 99% of the time, put the most likely case first, so the CPU doesn't have to jump. Speculation should help mitigate the rest.
2) A good reason why operator new() throws by default.