lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1433341792-2017-1-git-send-email-laijs@cn.fujitsu.com>
Date:	Wed, 3 Jun 2015 22:29:48 +0800
From:	Lai Jiangshan <laijs@...fujitsu.com>
To:	<linux-kernel@...r.kernel.org>
CC:	Lai Jiangshan <laijs@...fujitsu.com>, Tejun Heo <tj@...nel.org>
Subject: [PATCH 0/4 V3] workqueue: avoid creating identical pwqs

Hi,

In some conditions, the default pwq or the per-node pwq might be rebuilt identically,
it causes overhead. The code of this patchset checks the attrs and avoids it.

Patch1 adds get_pwq_unlocked() due to reusing old pwq in more cases
Patch2~3 avoid to create identical pwqs
Patch4 reuse wq_update_unbound_numa_attrs_buf, simple cleanup

changed from V2:
o	get_pwq_unlocked() returns void
o	move the check of the return value of alloc_unbound_pwq() into its branch
o	wq_update_unbound_numa_attrs_buf is renamed
o	kill get_alloc_node_unbound_pwq(), may or may not replement it in future

Cc: Tejun Heo <tj@...nel.org>

Lai Jiangshan (4):
  workqueue: introduce get_pwq_unlocked()
  workqueue: reuse the current per-node pwq when its attrs are unchanged
  workqueue: reuse the current default pwq when its attrs unchanged
  workqueue: reuse wq_update_unbound_numa_attrs_buf as temporary attrs

 kernel/workqueue.c | 94 ++++++++++++++++++++++++++++++++----------------------
 1 file changed, 56 insertions(+), 38 deletions(-)

-- 
2.1.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ