linux-kernel - Re: [PATCH 4/7 V2] workqueue: reuse the current per-node pwq when its attrs unchanged

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-prev] [day] [month] [year] [list]

Message-ID: <20150526185159.GL7099@htj.duckdns.org>
Date:	Tue, 26 May 2015 14:51:59 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Lai Jiangshan <laijs@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/7 V2] workqueue: reuse the current per-node pwq when
 its attrs unchanged

Hello, Lai.

On Mon, May 25, 2015 at 05:47:17PM +0800, Lai Jiangshan wrote:
> The patch 4/5/6 does reduce cpu and temporary-memory usage sometimes.
> But it is in slow path where small optimization is commonly unwelcome at.
> 
> Do I need to refactor the patches?  I'm in doubt for the necessary.

I like avoiding creating identical pwqs at least.  For the rest, I'm
okay either way as long as code is not made more complex in the
process.

Thanks.

-- 
tejun
--
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/