linux-kernel - Re: [PATCH 0/6] cpuset: convert to new cpumask API

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

Date:	Wed, 31 Dec 2008 03:56:17 -0800
From:	Mike Travis <travis@....com>
To:	Li Zefan <lizf@...fujitsu.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Paul Menage <menage@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/6] cpuset: convert to new cpumask API

Li Zefan wrote:
> This patchset converts cpuset to use new cpumask API, and thus
> remove on stack cpumask_t to reduce stack usage.
> 
> Before:
>  # cat kernel/cpuset.c include/linux/cpuset.h | grep -c cpumask_t
>  21
> After:
>  # cat kernel/cpuset.c include/linux/cpuset.h | grep -c cpumask_t
>  0
> 
> The patchset is based on mmotm 2008-12-30-16-05.
> 
> [PATCH 1/6] cpuset: remove on stack cpumask_t in cpuset_sprintf_cpulist()
> [PATCH 2/6] cpuset: remove on stack cpumask_t in cpuset_can_attach()
> [PATCH 3/6] cpuset: convert cpuset_attach() to use cpumask_var_t
> [PATCH 4/6] cpuset: don't allocate trial cpuset on stack
> [PATCH 5/6] cpuset: convert cpuset->cpus_allowed to cpumask_var_t
> [PATCH 6/6] cpuset: remove remaining pointers to cpumask_t
> ---
>  include/linux/cpuset.h   |   10 +
>  kernel/cpuset.c          |  279 ++++++++++++++++++++++++++++-------------------
>  3 files changed, 174 insertions(+), 115 deletions(-)
> 


These all look good Li!  Thanks for doing this.  You can add my:

Acked-by: Mike Travis <travis@....com>
--
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/