From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933251AbcE3OAG (ORCPT ); Mon, 30 May 2016 10:00:06 -0400 Received: from www.linutronix.de ([62.245.132.108]:54003 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932192AbcE3OAD (ORCPT ); Mon, 30 May 2016 10:00:03 -0400 Subject: Re: [patch V2 2/7] futex: Hash private futexes per process To: Peter Zijlstra References: <20160505204230.932454245@linutronix.de> <20160505204353.973009518@linutronix.de> <20160519122406.GA3192@twins.programming.kicks-ass.net> <20160527171001.GC28561@breakpoint.cc> <20160530085820.GN3192@twins.programming.kicks-ass.net> <9e7e4fb5-7b95-7676-d0f9-8e5dc5dc3ba9@linutronix.de> <20160530120630.GB3193@twins.programming.kicks-ass.net> <20160530134911.GD3193@twins.programming.kicks-ass.net> Cc: Sebastian Andrzej Siewior , Thomas Gleixner , LKML , Linus Torvalds , Darren Hart , Ingo Molnar , Michael Kerrisk , Davidlohr Bueso , Chris Mason , "Carlos O'Donell" , Torvald Riegel , Eric Dumazet From: Sebastian Andrzej Siewior Message-ID: Date: Mon, 30 May 2016 15:59:51 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.1.0 MIME-Version: 1.0 In-Reply-To: <20160530134911.GD3193@twins.programming.kicks-ass.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/30/2016 03:49 PM, Peter Zijlstra wrote: >> The same thing can happen within a Task if you take my story from above >> and replace task with thread. Completely understood. > > Right; so I don't see the point of PREALLOCATE_HASH to cater for RT > workloads if it still doesn't guarantee anything, esp. if the failure > case is silent and obscure. So what do you suggest? Adding trace points in order to learn about possible collisions or using tickets (on top of this) to guarantee being collision free? Note: this as it, is already a win on NUMA boxes since the memory is not referenced cross node. Sebastian