lkml.org 
[lkml]   [1999]   [May]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: kernel_lock() profiling results
    Hi,

    On Wed, 26 May 1999 19:41:11 +0200, Manfred Spraul
    <manfreds@colorfullife.com> said:

    > 1) Andrea noticed that 'unlock_kernel()' only releases the kernel lock
    > if the lock was obtained once.

    Yes, but in all the places we are currently doing the copy_*_user, we
    only hold the lock once. In general we might want to do a true
    save/restore of lock_depth for a new, self-unlocking copy_*_user, but
    right now the droplock diffs still do the right thing the simple way.

    --Stephen

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

    \
     
     \ /
      Last update: 2005-03-22 13:51    [W:2.655 / U:0.040 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site