News for hackers. Stuff that matters.
Re:The Greatest Bug of All by dhess on Tuesday July 08, 2008 @01:47AM (#239618)
Typically a system call only leads to a context switch if the call will block, or if the caller has used up its timeslice; otherwise, it's just a couple of relatively cheap protection domain crossings.
Re:The Greatest Bug of All by ajross on Tuesday July 08, 2008 @10:08AM (#239852)
A system call is a pair of context switches: swap the registers, swap the stack, change the TLB mappings, on some architectures flush the cache. Even the fastest system calls (Linux on amd64) take a thousand clock cycles or more.
Re:The Greatest Bug of All by dhess on Tuesday July 08, 2008 @07:48PM (#240537)
Why would you flush the cache on a system call?? The only case I can think of where a cache flush is needed at all is if you have a virtually-addressed (or -indexed) cache and you're switching address spaces. Some ARM implementations may do this, if I recall correctly. But entering the kernel doesn't require an address space switch because the kernel is mapped into every process's address space, at the same virtual address.

Also, as I pointed out below, typically you don't even need to change any TLB entries on kernel entry, because the address space doesn't change and the kernel TLB mappings are usually pinned. In other words, any load from or store to a kernel page will always hit the TLB.

On most architectures, you probably don't even need to swap registers; not the general-purpose ones, anyway.

Sorry, but you're confusing switching processes with switching privilege, and greatly overestimating the cost of a system call.

Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @11:16AM (#239919)
Technically, a system call (on i386) is only changing CS, EIP, and ESP. You don't have to change CR3 or flush the TLB. "Swapping stacks" isn't expensive.
Re:The Greatest Bug of All by ajross on Tuesday July 08, 2008 @11:37AM (#239942)
It's a thousand clock cycles more than a function call (seriously, I'm not making this up: time it sometime). I guess whether that is "expensive" or not is context dependent. For some applications (e.g. database servers) that make lots of random access reads from large files, using a mapping can be overwhelmingly faster.

I guess I'm stunned that this turns out to have been such a controversial notion...

Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @11:56AM (#239969)
Can you be specific about which part of the system call you're talking about? Because you said "swapping the stack" (which doesn't take a thousand clock cycles) and "flushing the TLB" (which doesn't happen in OSs where the kernel occupies a permanent part of the VM address space).

I'm sorry, this isn't controversial. All I said was, "mmap isn't faster than read in typical use cases". But then we all got really specific talking about ESP and CS and CR3 and now we have something to go back and forth on, which is kind of fun, and I might learn something new. Didn't mean to snipe at you.

Re:The Greatest Bug of All by ajross on Tuesday July 08, 2008 @12:12PM (#239990)
To be clear: I didn't say "flush the TLB". Nonetheless unless you happen to be lucky and have those kernel mapping in there, those TLB entries need to be faulted in. That's expensive. Likewise the new stack isn't in L1 cache and needs to be read in from main memory. Likewise the kernel code to execute the handler needs to be read into the instruction cache, etc...

Given that main memory reads are pushing 100 cycles on a modern box, all those things add up. A context switch (my usage: meaning a bounce to a non-local, non-current execution environment) is really expensive.

Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @01:51PM (#240100)
Come on. Userland code constantly blows L1 cache. Almost any library call will churn the icache. For that matter, any memory access can collide the TLB. None of those things are syscall-specific. If you were concerned about L1 and icache, you needed to write your code meticulously to accomodate them anyways.

Yes, cache is important. But there's a world of difference between the "flush the caches and the TLB" behavior that system calls used to incur and the "expensive relative to local variable access" behavior we're talking about here.

"A bounce to non-local, non-current execution environment" literally doesn't mean anything. You could be talking about the CR3 change that swaps page hierarchies, the CPL3->0 change that allows privileged instructions, the CS change that got you there, or even the ESP change to "swap stacks". Which of these are expensive?

I'm chasing you down because it's fun, not because I think you don't know what you're talking about.

But, let's make this relevant: if system call overhead is drowned by disk I/O overhead, then one argument for mmap goes away.

Re:The Greatest Bug of All by ajross on Tuesday July 08, 2008 @02:21PM (#240143)
Why do you insist on making this a flame war? Sit down and write a program that makes 10M trivial system calls (getpid() is a good choice) and one that calls a function to return a constant integer 10M times.

I'm sorry, but you seem to have a wildly inflated idea of the speed of system calls on modern OSs. The real world just doesn't work like that. This is my last post on this thread.

Re:The Greatest Bug of All by spc476 on Wednesday July 09, 2008 @03:04AM (#240874)
I did that a few months ago (http://boston.conman.org/2007/11/30.1) and found some surprising results (http://boston.conman.org/2007/12/02.1)which showed that using getpid() wasn't a good test of system call overhead.
Re:The Greatest Bug of All by tptacek on Wednesday July 09, 2008 @03:21AM (#240888)
That is a really nice catch.
Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @06:49PM (#240471)
By the way, you asked me to time getpid against "a function that returns a constant integer". Obviously that's a silly comparison (getpid isn't really returning a constant; it's a vectored call and it has to pull the PID out of a structure offset from %%fs). But here's a fairer fight: getpid vs. a trivial LFSR:

        s = (s >> 1) ^ (-(s & 1) & 0xd0000001);
I also timed it the way you asked, with wall clock time over 100M iterations (10M runs too fast to time). Surprising even me, getpid wins by almost a full second.

Got another challenge for me to write code for?

Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @04:12PM (#240292)
Here you go:

http://pastie.org/230109

Want the punch line? OSX getpid averages under 100 cycles; snprintf (no IO) averages over 1000.

Re:The Greatest Bug of All by ajross on Tuesday July 08, 2008 @06:58PM (#240480)
Are you sure getpid() is doing a system call and not reading TLS?
Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @07:27PM (#240508)
What a great question! I just checked. Nope:

Breakpoint 1, 0x96210c44 in getpid ()

(gdb) disp/i $eip

2: x/i $eip 0x96210c44 <getpid>: call 0x96210c49 <getpid+5>

(gdb) stepi

0x96210c49 in getpid ()

2: x/i $eip 0x96210c49 <getpid+5>: pop %ecx

0x96210c4a in getpid ()

2: x/i $eip 0x96210c4a <getpid+6>: lea 0xa6427a3(%ecx),%ecx

0x96210c50 in getpid ()

2: x/i $eip 0x96210c50 <getpid+12>: mov (%ecx),%eax

0x96210c52 in getpid ()

2: x/i $eip 0x96210c52 <getpid+14>: test %eax,%eax

0x96210c54 in getpid ()

2: x/i $eip 0x96210c54 <getpid+16>: jle 0x96210c57 <getpid+19>

0x96210c57 in getpid () 2: x/i $eip 0x96210c57 <getpid+19>: mov $0x14,%eax

0x96210c5c in getpid ()

2: x/i $eip 0x96210c5c <getpid+24>: call 0x961e8cf4 <_sysenter_trap>

Re:The Greatest Bug of All by dhess on Tuesday July 08, 2008 @07:29PM (#240511)
"TLB entries need to be faulted in?" You mean TLB entries which map kernel pages?

Typically kernel pages (and the TLB entries which cover them) are "pinned." You don't want to take a TLB exception in the middle of an interrupt service routine, let alone a page fault. Most architectures couldn't even handle the nested exception, and would panic.

Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @07:42PM (#240528)
TLB misses don't cause exceptions on X86. The TLB is part of the microarchitecture.
Re:The Greatest Bug of All by dhess on Tuesday July 08, 2008 @07:59PM (#240548)
Yeah, also on IA-64 (optionally). I was generalizing. Still, on IA-64 at least, you would typically pin kernel mappings by putting them in translation registers instead of translation cache registers (i.e., the TLB).

I haven't kept up with x86 on Linux; does Linux enable the global page extensions? I would assume it does for kernel mappings.

Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @02:18AM (#239633)
A read from the disk is always going to sleep the process.
Re:The Greatest Bug of All by dhess on Tuesday July 08, 2008 @03:00AM (#239648)
Yes, regardless of the mechanism that causes the disk read.

Given a particular access pattern, whether the disk gets read or not is independent of the choice to use seek+read or mmap. System calls that don't block don't cause a context switch (1). Therefore, the occurrence of context switches due to disk reads is also independent of the choice to use seek+read or mmap, so trying to avoid context switches isn't a reason to use one or the other.

(1) modulo the timeslice expiring during the system call, which could actually help the system call case since there's no need to take an interrupt from user space when the timeslice expires due to a timer: the system call can be predicted since it's in the code stream, but the interrupt can't be. Anyway, that's all in the noise.)

Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @03:06AM (#239650)
I agree with you, but you just refuted the argument you made one comment back. =)
Re:The Greatest Bug of All by dhess on Tuesday July 08, 2008 @03:16AM (#239659)
No, I didn't :) All I did in my original comment was simply to point out to ajross that system calls don't always cause context switches. It's a common misconception, not unique to ajross, of course, that a protection domain crossing requires a context switch, so I was making what I hoped was a helpful observation. I didn't say anything at all about disk reads in that original comment, nor about the merits of mmap vs. seek+read!

I'm glad we agree on my second comment, in any case. :)

Re:The Greatest Bug of All by ajross on Tuesday July 08, 2008 @10:12AM (#239855)
I think we're quibbling about terminology. I'm not sure of the difference between a "protection domain crossing" (not a common term, AFAIK) and a "context switch" (pervasive jargon). You seem to be indicating that the latter always involves a separate process, which of course is more expensive (on most architectures) due to cache issues. I'm using the term to mean a switch between two execution domains.
Re:The Greatest Bug of All by dhess on Tuesday July 08, 2008 @07:23PM (#240506)
Sorry, you're right, "protection domain crossing" probably isn't common jargon. It's a holdover from my time as a processor architect on IA-64. It means privilege escalation.

Anyway, in any common parlance of the term "context switch" I've ever seen, the amount of state switched to take a system call is much less (edit: oops, originally said 'greater' ;) than the amount of state switched in a context switch. At the very least, a context switch should mean the save and restore of user-level register state, which isn't necessary for a system call. You certainly wouldn't want to do that just to make a system call on a typical RISC architecture with 30-something registers! After all, from the perspective of the caller, it's just a special procedure call. The compiler and system call entry point can even use the same argument-passing convention.

I wrote at least part of (maybe most, can't remember anymore :) the "recommended" context switch handler for IA-64. It was significantly more expensive than the system call handler. IA-64 dedicated quite a bit of hardware to making system calls cheap. If I recall correctly, besides a few privileged registers, the only thing we changed was the location of the register stack engine's backing store. That's just a single user-level register. (You don't want to spill registers with potentially privileged state into user space.)

Anyway, this is way off-topic now and I don't think anybody's interested other than the three of us, so that's the last I'll say about it.

Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @09:46PM (#240635)
Well, here's where this gets fun: most of the kernels we work with are structured like event loops, and disk I/O is asynchronous. When you issue a read vnop in a Unix kernel, your process will probably yield back to the scheduler loop, incurring the out switch and the in switch.

This mmap vs. read argument is as old as the hills. I picked a side a long time ago; keep it simple.