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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1163005750.14238.19.camel@twins>
Date:	Wed, 08 Nov 2006 18:09:10 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Paul Jackson <pj@....com>
Cc:	clameter@....com, akpm@...l.org, linux-kernel@...r.kernel.org
Subject: Re: Avoid allocating during interleave from almost full nodes

On Wed, 2006-11-08 at 09:06 -0800, Paul Jackson wrote:
> Peter wrote:
> > global fault counter
> 
> I hope we avoid frequently updated, widely accessed global
> counters.  They tend to create hot cache lines on big NUMA
> boxes.
> 
> Christoph said that the counters he was suggesting were
> node or cpu local.  That sounds good to me.

Very true indeed, I was just hoping we could come up with 1 vm-time; but
perhaps the local vs global thing will keep us from that.


-
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/