Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750862AbWA3Vcz (ORCPT ); Mon, 30 Jan 2006 16:32:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751291AbWA3Vcz (ORCPT ); Mon, 30 Jan 2006 16:32:55 -0500 Received: from mf00.sitadelle.com ([212.94.174.67]:25046 "EHLO smtp.cegetel.net") by vger.kernel.org with ESMTP id S1750862AbWA3Vcy (ORCPT ); Mon, 30 Jan 2006 16:32:54 -0500 Message-ID: <43DE8604.1060109@cosmosbay.com> Date: Mon, 30 Jan 2006 22:32:52 +0100 From: Eric Dumazet User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: "Eric W. Biederman" Cc: Greg KH , linux-kernel@vger.kernel.org, vserver@list.linux-vserver.org, Herbert Poetzl , "Serge E. Hallyn" , Alan Cox , Dave Hansen , Arjan van de Ven , Suleiman Souhlal , Hubertus Franke , Cedric Le Goater , Kyle Moffett Subject: Re: [PATCH 1/5] pid: Implement task references. References: <20060129190539.GA26794@kroah.com> <20060130045153.GC13244@kroah.com> <43DDA1E7.5010109@cosmosbay.com> <20060130184302.GA17457@kroah.com> <43DE6FE6.40705@cosmosbay.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2169 Lines: 65 Eric W. Biederman a ?crit : > Eric Dumazet writes: > >> Greg KH a ?crit : >>> On Mon, Jan 30, 2006 at 06:19:35AM +0100, Eric Dumazet wrote: >>>> Example of improvement in kref_put() : >>>> >>>> [PATCH] kref : Avoid an atomic operation in kref_put() when the last >>>> reference is dropped. On most platforms, atomic_read() is a plan read of the >>>> counter and involves no atomic at all. >>> No, we wat to decrement and test at the same time, to protect against >>> any race where someone is incrementing right when we are dropping the >>> last reference. >> Sorry ? Me confused ! > > Largely I think you have the right of it, that the optimization is > correct. My biggest complaint is that the common case is going to be > several references to the data structure. Releasing the references > will always be slow. To do the read you need to get the value into > the cache line. > > So it looks to me like you are optimizing the wrong case and > bloating the icache with unnecessary code. This function is not inlined. Adding a test and a branch is a matter of 7 bytes. 'Bloating the icache' is a litle bit off :) Avoiding an atomic is important. This is already done elsewhere in the kernel, in a inlined function with *many* call sites : (See kfree_skb() in include/linux//skbuff.h ) /* * If users == 1, we are the only owner and are can avoid redundant * atomic change. */ /** * kfree_skb - free an sk_buff * @skb: buffer to free * * Drop a reference to the buffer and free it if the usage count has * hit zero. */ static inline void kfree_skb(struct sk_buff *skb) { if (likely(atomic_read(&skb->users) == 1)) smp_rmb(); else if (likely(!atomic_dec_and_test(&skb->users))) return; __kfree_skb(skb); } This is a valid optimization : an atomic_dec_and_test() is very expensive. Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/