> Okay, so "locking the kernel" is really a misnomer.
These days it is, yes. Back in 2.0 and earlier days, it was pretty accurate.
I only started meddling with kernel source in late 2.1 days; I'd always assumed
that in 2.0, every syscall grabbed the kernel lock in its own code, I finally
checked the other day and discovered that the architecture dependent syscall
handler actually does it automatically for everything.
-- "House Plants are for ornamental use only and not for consumption" Notice in Sainsbury's Supermarket, London - Daily Mail- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/