lkml.org 
[lkml]   [1999]   [May]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: kernel_lock() profiling results
On Wed, 26 May 1999, Stephen C. Tweedie wrote:

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

I wouldn't call it the "right thing". It's also not simpler according to
me since to make sure that the unlock_kernel is really dropping the
kernel_flag spinlock you must check all entry paths and verify that
lock_depth is 0 at such time.

Andrea Arcangeli


-
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:0.667 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site