lkml.org 
[lkml]   [2000]   [Jan]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Lock granularity...
Date
From
> While i've been working with the linux kernel, i've noticed some definate
> performance bottlenecks in its implementation, and one of them is the incredible

Have you measured them

> 2.3.40, i just ran a simple grep to find the calls to lock_kernel, and
> found 451. I was wondering if there are any groups out there that are addressing
> this problem specifically, or any general strategy for addressing the number
> of global kernel locks? (Especially since some of them seem to be used
> with relatively orthogonal things... ;-)

Thats the whole point of lock_kernel() its a generic low cost lock that
preserves traditional unix semantics (its dropped by magic on sleeping
and retaken by magic on wakeups).

We don't want hundreds of silly locks for non performance critical paths.


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