Paul M wrote:
> cpuset.c:update_nodemask() uses a write_lock_irq() on tasklist_lock to
> block concurrent forks; a read_lock() suffices and is less intrusive.
Seems reasonable to me - thanks.
> - write_lock_irq(_lock); /* block fork */
> + read_lock(_lock);
cpuset.c:update_nodemask() uses a write_lock_irq() on tasklist_lock to
block concurrent forks; a read_lock() suffices and is less intrusive.
Signed-off-by: Paul Menage<[EMAIL PROTECTED]>
---
kernel/cpuset.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Index:
cpuset.c:update_nodemask() uses a write_lock_irq() on tasklist_lock to
block concurrent forks; a read_lock() suffices and is less intrusive.
Signed-off-by: Paul Menage[EMAIL PROTECTED]
---
kernel/cpuset.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Index:
Paul M wrote:
cpuset.c:update_nodemask() uses a write_lock_irq() on tasklist_lock to
block concurrent forks; a read_lock() suffices and is less intrusive.
Seems reasonable to me - thanks.
- write_lock_irq(tasklist_lock); /* block fork */
+
4 matches
Mail list logo