On Wed, 29 June 2005 11:48:25 -0400, Steven Rostedt wrote:
> On Wed, 29 Jun 2005, Jörn Engel wrote:
>
> > All nice and well. But still, for the sake of simplicity and me not
> > wanting to think, I prefer always using spin_lock_irqsave for
> > everything. Since when should I stop and think about my own code?
>
> OK, I use spin_lock_irqsave first, and then I only use spin_lock when I
> already know interrupts are off. But the locks I usually use are used by
> interrupts and that is reason enough to use it. I wouldn't use the
> _irqsave for simplicity, I use it since I still believe it keeps latency
> down for SMP.
Ok, before even more people get confused - I was joking. Simple code
is obviously a good thing to have. Not thinking about code, well...
> > In fact, why don't we all sit down and start using KCSP for kernel
> > hacking? ;)
>
> Naw, I'm doing my PhD on implemting Linux drivers in SmallTalk. That will
> make everybody happy!
... but it appears as if you got the joke.
Jörn
--
Public Domain - Free as in Beer
General Public - Free as in Speech
BSD License - Free as in Enterprise
Shared Source - Free as in "Work will make you..."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
