From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932239AbWATWQo (ORCPT ); Fri, 20 Jan 2006 17:16:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932240AbWATWQo (ORCPT ); Fri, 20 Jan 2006 17:16:44 -0500 Received: from smtp.osdl.org ([65.172.181.4]:2969 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S932239AbWATWQn (ORCPT ); Fri, 20 Jan 2006 17:16:43 -0500 Date: Fri, 20 Jan 2006 14:18:01 -0800 From: Andrew Morton To: Ingo Oeser Cc: linux-kernel@vger.kernel.org, dsingleton@mvista.com, drepper@gmail.com, mingo@elte.hu Subject: Re: [robust-futex-4] futex: robust futex support Message-Id: <20060120141801.71d842f7.akpm@osdl.org> In-Reply-To: <200601201841.24565.ioe-lkml@rameria.de> References: <43C84D4B.70407@mvista.com> <20060118212256.1553b0ec.akpm@osdl.org> <200601201841.24565.ioe-lkml@rameria.de> X-Mailer: Sylpheed version 1.0.0 (GTK+ 1.2.10; i386-vine-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ingo Oeser wrote: > > > > + list_for_each_entry_safe(this, next, head, list) { > > > + list_del(&this->list); > > > + kmem_cache_free(robust_futex_cachep, this); > > > + } > > > > If we're throwing away the entire contents of the list, there's no need to > > detach items as we go. > > Couldn't even detach the list elements first by > > list_splice_init(&mapping->robust_head->robust_list, head); > > and free the list from "head" after releasing the mutex? > This would reduce lock contention, no? Yes, it would reduce lock contention nicely.