Re: [PATCH #2] console lock grabbed too early in printk...

From: Chris Lattner (sabre@skylab.org)
Date: Mon Jul 03 2000 - 17:36:25 EST


> > is not held (which is the only case that matters, because otherwise,
> > access would block on the console_lock currently), we have the following
> > (for the x86 at least, the others are similar):
> >
> > spin_lock:
> > "xchgb %b0,%1"

> The xchgb is a locked bus access so takes an awful lot longer, especially on
> earlier cpus

Okay, so especially in SMP systems where you actually have to lock a
bus... the xchg could take a few cycles... but the question remains, how
frequently is printk called? Is it called "that often" that even 100
cycles can't be spared?

-Chris

-
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/



This archive was generated by hypermail 2b29 : Fri Jul 07 2000 - 21:00:13 EST