lkml.org 
[lkml]   [2001]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: SMP spin-locks
    Hi!

    > The 'read()' routine uses a spinlock when it modifies pointers.
    >
    > I started to look into where all the CPU clocks were going. The
    > SMP spinlock code is where it's going. There is often contention
    > for the lock because interrupts normally occur at 50 to 60 kHz.
    >
    > When there is contention, a very long........jump occurs into
    > the test.lock segment. I think this is flushing queues.

    On UP, there's *never* contention on the lock, because irqsave lock
    disables interrupts. Right? Something else must be slowing you.

    Pavel
    PS: But that's bad. Performance should not come down twice --
    this will bite you even on real SMP.

    --
    Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
    details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 12:55    [W:0.028 / U:0.052 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site