linux-kernel - Re: [PATCH -mm] cgroup,cpuset: use alternative malloc to allocate large memory buf for tasks

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]

Message-Id: <20080911055630.b50e8717.pj@sgi.com>
Date:	Thu, 11 Sep 2008 05:56:30 -0500
From:	Paul Jackson <pj@....com>
To:	Lai Jiangshan <laijs@...fujitsu.com>
Cc:	akpm@...ux-foundation.org, menage@...gle.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm] cgroup,cpuset: use alternative malloc to allocate
 large memory buf for tasks

Lai Jiangshan wrote:
> This new alternative allocation implementation can allocate memory
> up to 64M in 32bits system or 512M in 64bits system.

Just a random idea - it seems to me that this new allocation
implementation might be more generally useful than just for cgroups.

So, instead of having cgroup_huge_mem_alloc() and cgroup_huge_mem_free()
in kernel/cgroup.c, one might have say big_kmalloc() and big_kfree() in
some mm/*.c file.  I used "big" instead of "huge" or "compound" or
"large", as these other adjectives already have other meanings in these
allocator functions.

However ... I would suggest that you do not spend anytime implementing
the above idea unless either (1) it strikes you as absolutely brilliant,
or (2) Paul Menage endorses it.  Paul M has been paying closer attention
to this change than I have, so his recommendations are worth far more
than mine are here.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.940.382.4214
--
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/