[lkml]   [2000]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH #2] console lock grabbed too early in printk...
    > > 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?


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:57    [W:0.037 / U:7.696 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site