linux-kernel - Re: Avoid allocating during interleave from almost full nodes

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

Message-ID: <Pine.LNX.4.64.0612010823170.17445@schroedinger.engr.sgi.com>
Date:	Fri, 1 Dec 2006 08:27:35 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	Paul Jackson <pj@....com>
cc:	akpm@...l.org, linux-kernel@...r.kernel.org
Subject: Re: Avoid allocating during interleave from almost full nodes

On Thu, 30 Nov 2006, Paul Jackson wrote:

> Anybody have any idea which is the case?

You can rely on those to increment and count events if it does not matter 
that we may miss an event once in a while. And I think that is the case 
here.

The counters may only switched off for embedded systems. We could just 
remove the CONFIG option if necessary. The event counter operations are in 
critical paths of the VM though and I would think that embedded systems 
with no need for vmstat want those as efficient as possible.
-
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/