linux-kernel - Re: What was the problem with quicklists and x86-64?

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]

Date:	Thu, 13 Dec 2007 13:33:32 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>, Andi Kleen <ak@...e.de>,
	Tony Luck <tony.luck@...el.com>,
	Asit Mallick <asit.k.mallick@...el.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: What was the problem with quicklists and x86-64?

On Fri, 14 Dec 2007, Benjamin Herrenschmidt wrote:

> > This is a generic NUMA issue here! Quicklist pages that are not on 
> > the current node are freed without waiting for the TLB flush. The patch 
> > that I posted fixes that by requiring that all pages be flushed. 
> 
> Ah ok, so that's a NUMA issue due to how the quicklists are implemented,
> I see. Note that the flush isn't necessary a solution on all platforms.
> On powerpc, I -still- need to defer with RCU as we don't do anything in
> flush tlb. Our TLB invalidations are HW broadcast in the first place,
> but what we need to sync with is the SW hash reload code.
> 
> So your solution in the quicklists doesn't solve the problem for us.

No this may mean that the problem does not exist on powerpc since it 
seems to be okay to free pages before all processors have flushed the 
TLBs? Or are you deferrring the freeing of the pages via RCU?


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