2006/10/9, Kip Macy <kmacy_at_fsmware.com>: > > > > How would you see a sched_lock decomposition (and, if it is possible, > > how many locks it could be decomposed in?) > > Rather than having a per thread lock, Solaris uses the lock for the > current container that a thread is associated with (cpu, run queue, > sleep queue, etc.) to serialize thread updates. I think this is probably > the best approach. A per proess spin lock would not scale well for large > multi-threaded apps. Yes, this is what I was thinking to. Maybe sched_lock could be reworked when all the other issues about SMPng would be closed. IIRC, somebody was speaking about the starting of a new project which was related to the analisys and decomposition of the more contentive locks. Attilio -- Peace can only be achieved by understanding - A. EinsteinReceived on Sun Oct 08 2006 - 21:03:44 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:01 UTC