lkml.org 
[lkml]   [2002]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Lse-tech] lockmeter results comparing 2.4.17, 2.5.3, and 2.5.5
> inode_lock hold times are a problem for other reasons.  Leaving this
> unfixed makes the preepmtible kernel rather pointless.... An ideal
> fix would be to release inodes based on VM pressure against their backing
> page. But I don't think anyone's started looking at inode_lock yet.
>
> The big one is lru_list_lock, of course. I'll be releasing code in
> the next couple of days which should take that off the map. Testing
> would be appreciated.

Seeing as people seem to be interested ... there are some big holders
of BKL around too - do_exit shows up badly (50ms in the data Hanna
posted, and I've seen that a lot before). I've seen sync_old_buffers
hold the BKL for 64ms on an 8way Specweb99 run (22Gb of RAM?)
(though this was on an older 2.4 kernel, and might be fixed by now).

M.
-
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 13:20    [W:0.083 / U:3.608 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site