Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933146AbbFCPBw (ORCPT ); Wed, 3 Jun 2015 11:01:52 -0400 Received: from cn.fujitsu.com ([59.151.112.132]:51338 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S932600AbbFCPBh (ORCPT ); Wed, 3 Jun 2015 11:01:37 -0400 X-IronPort-AV: E=Sophos;i="5.01,1,1399996800"; d="scan'208";a="96378544" From: Lai Jiangshan To: CC: Lai Jiangshan , Tejun Heo Subject: [PATCH 0/4 V3] workqueue: avoid creating identical pwqs Date: Wed, 3 Jun 2015 22:29:48 +0800 Message-ID: <1433341792-2017-1-git-send-email-laijs@cn.fujitsu.com> X-Mailer: git-send-email 2.1.0 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.167.226.103] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1283 Lines: 34 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 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/