starve other threads from the resource lock for a long time in
case of long waiting queue, so change the debug level from
D_OTHER to the less frequently used D_INFO.
b=15953
i=adilger
i=nathan.rutman
this allows us to quickly find what pages to write and remove
once lock callback is received.
+Severity : normal
+Bugzilla : 15953
+Description: more ldlm soft lockups
+Details : In ldlm_resource_add_lock(), call to ldlm_resource_dump()
+ starve other threads from the resource lock for a long time in
+ case of long waiting queue, so change the debug level from
+ D_OTHER to the less frequently used D_INFO.
+
--------------------------------------------------------------------------------
2007-08-10 Cluster File Systems, Inc. <info@clusterfs.com>
{
check_res_locked(res);
- ldlm_resource_dump(D_OTHER, res);
- CDEBUG(D_OTHER, "About to add this lock:\n");
- ldlm_lock_dump(D_OTHER, lock, 0);
+ ldlm_resource_dump(D_INFO, res);
+ CDEBUG(D_INFO, "About to add this lock:\n");
+ ldlm_lock_dump(D_INFO, lock, 0);
if (lock->l_destroyed) {
CDEBUG(D_OTHER, "Lock destroyed, not adding to resource\n");