| 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
| ||
|
Date: Sat, 27 Jul 2013 00:55:12 +0800 From: Lai Jiangshan <eag0628@...il.com> To: Tejun Heo <tj@...nel.org>, Lai Jiangshan <laijs@...fujitsu.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH] workqueue: clear workers of a pool after the CPU is offline On Fri, Jul 26, 2013 at 6:22 PM, Tejun Heo <tj@...nel.org> wrote: > On Fri, Jul 26, 2013 at 11:47:04AM +0800, Lai Jiangshan wrote: >> any worker can't kill itself. >> managers always tries to leave 2 workers. >> >> so the workers of the offline cpu pool can't be totally destroyed. > > But we *do* want to keep them around as CPUs taken offline are likely > to come online at some point and destroying all of them saves only > ~16k of memory while adding more work while CPUs are on/offlined which 4 threads, (normal and high priority wq) ~32k it is still small. > can be very frequent on mobile devices. The change was *intentional*. but sometimes the cpu is offline for long time. and maybe the adminstrator want to reclaim the resource.. Add a boot option or sysfs switch? > > 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/ -- 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