http://defect.opensolaris.org/bz/show_bug.cgi?id=11603
Michael Hunter <michael.hunter at sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michael.hunter at sun.com
--- Comment #1 from Michael Hunter <michael.hunter at sun.com> 2009-09-28
23:24:18 UTC ---
(In reply to comment #0)
> In nwamd, when trying to obtain a particular configuration object's lock, we
> hold the object list lock to ensure that the list is not changed while we're
> waiting
> for the object.
It is a reader/writer lock and we only hold the reader side when walking the
list to find an object.
> Problem is, if another thread has the object locked, we will
> have a waiting thread holding the lock for the entire object list. As a
> consequence, for example, no ENMs can be retrieved if thread A holds object X
> and thread B is waiting for it. This has practical consequences, e.g. when we
> run "nwamadm list" when the daemon is busy it can be quite slow.
We should look more closely at this example (probably with dtrace) to see what
the contention is over.
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
