linux-kernel - Re: + kmap-types-clean-up-and-optimization.patch added to -mm tree

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

Message-ID: <1293098310.2170.415.camel@laptop>
Date:	Thu, 23 Dec 2010 10:58:30 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	akpm@...ux-foundation.org
Cc:	mm-commits@...r.kernel.org, JBeulich@...ell.com, hpa@...or.com,
	mingo@...e.hu, tglx@...utronix.de,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: + kmap-types-clean-up-and-optimization.patch added to -mm tree

On Wed, 2010-12-22 at 14:48 -0800, akpm@...ux-foundation.org wrote:
> The patch titled
>      kmap-types: clean up and optimization
> has been added to the -mm tree.  Its filename is
>      kmap-types-clean-up-and-optimization.patch
> 
> Before you just go and hit "reply", please:
>    a) Consider who else should be cc'ed
>    b) Prefer to cc a suitable mailing list as well
>    c) Ideally: find the original patch on the mailing list and do a
>       reply-to-all to that, adding suitable additional cc's
> 

> ------------------------------------------------------
> Subject: kmap-types: clean up and optimization
> From: "Jan Beulich" <JBeulich@...ell.com>
> 
> Several of the types aren't being used at all anymore - those can be
> deleted altogether.  

NO! That's wrong, in fact non of them are being used, but removing them
will decrease the number of kmap_atomic slots, but those are still being
used.

> Others are used only by single components that can be
> assumed to be enabled everywhere, so those are made dependent upon
> CONFIG_* settings.  Since this somewhat conflicts with the sequential gap
> markers used under __WITH_KM_FENCE, and since this can be simplified
> anyway, fold the enumerator definitions with the (modified accordingly)
> KMAP_D() macro always.
> 
> The whole point of the reduction is that, at least on ix86, the number of
> kmap types can (depending on configuration) affect the amount of low
> memory, and thus unused types should be avoided if possible.

Feh, its only a few pages and since there is no way to actually tell if
you've got enough kmap atomic pages other than experiencing runtime
errors, removing them must be done with utmost prudence.

> Signed-off-by: Jan Beulich <jbeulich@...ell.com>

Nacked-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
--
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/