Messages in this thread | | | Date | Tue, 25 Apr 2006 20:19:58 +0300 | From | Avi Kivity <> | Subject | Re: Compiling C++ modules |
| |
Dmitry Torokhov wrote: >>> TakeLock l(&lock); >>> >>> do_something(); >>> do_something_else(); >>> >>> First of all, that extra TakeLock object chews up stack, at least 4 or >>> 8 bytes of it, depending on your word size. >>> >> No, it's optimized out. gcc notices that &lock doesn't change and that >> 'l' never escapes the function. >> > > "l" that propects critical section gets thrown away??? Calm down, the storage for 'l' is thrown away, but its effects remain. > What is the > name of the filesystem you ported? I mean, I need to know so I don't > use it by accident. > It's very expensive, you can't use it by accident.
-- Do not meddle in the internals of kernels, for they are subtle and quick to panic.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |