linux-kernel - Re: [patch 0/4] Cpu alloc V5: Replace percpu allocator in modules.c

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 20 Sep 2008 00:28:02 +0900
From:	"KOSAKI Motohiro" <m-kosaki@...es.dti.ne.jp>
To:	"Christoph Lameter" <cl@...ux-foundation.org>
Cc:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, jeremy@...p.org, ebiederm@...ssion.com,
	travis@....com, herbert@...dor.apana.org.au, xemul@...nvz.org,
	penberg@...helsinki.fi
Subject: Re: [patch 0/4] Cpu alloc V5: Replace percpu allocator in modules.c

Hi Cristoph,

> Just do the bare mininum to establish a per cpu allocator. Later patchsets
> will gradually build out the functionality.
>
> The most critical issue that came up on the last round is how to configure
> the size of the percpu area. Here we simply use a kernel parameter and use
> the static size of the existing percpu allocator for modules as a default.
>
> The effect of this patchset is to make the size of percpu data for modules
> configurable. Its no longer fixed at 8000 bytes.

I don't know so much this area.
Could you please what are the problem that you think　about?

performance?
fixed-size cause per-cpu starvation by huge user?
--
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/