http://defect.opensolaris.org/bz/show_bug.cgi?id=11603
Summary: nwamd's object locking scheme is too coarse
Classification: Development
Product: nwam
Version: unspecified
Platform: ANY/Generic
OS/Version: All
Status: ACCEPTED
Severity: enhancement
Priority: P3
Component: ON daemon
AssignedTo: nwam-dev at opensolaris.org
ReportedBy: alan.maguire at sun.com
QAContact: nwam-dev at opensolaris.org
--- Comment #0 from amaguire <alan.maguire at sun.com> 2009-09-28 19:26:48 UTC
---
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. 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.
--
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.
