[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
initialized state of capability objects should be locked
From: |
Neal H. Walfield |
Subject: |
initialized state of capability objects should be locked |
Date: |
Sun, 16 Jan 2005 13:09:47 -0500 |
User-agent: |
Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.3 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI) |
When a capability object is returned to the user (via
hurd_cap_class_alloc), it is locked. hurd_cap_class_alloc does the
lock manually. When a capability is released, _hurd_cap_obj_dealloc
is called. _hurd_cap_obj_dealloc takes a locked capability and
returns it to the slab after unlocking it. We should change the
initialization state so that _hurd_cap_obj_constructor enters locked
objects into the slab thereby eliding this extra lock/unlock sequence.
Marcus, shall I commit a patch which does this?
Thanks,
Neal
- initialized state of capability objects should be locked,
Neal H. Walfield <=