Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 1 Mar 2003 07:24:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 1 Mar 2003 07:24:02 -0500 Received: from tomts25.bellnexxia.net ([209.226.175.188]:58542 "EHLO tomts25-srv.bellnexxia.net") by vger.kernel.org with ESMTP id ; Sat, 1 Mar 2003 07:24:02 -0500 From: Ed Tomlinson Organization: me To: Andi Kleen Subject: Re: [PATCH] New dcache / inode hash tuning patch Date: Sat, 1 Mar 2003 07:34:44 -0500 User-Agent: KMail/1.5.9 Cc: Andi Kleen , linux-kernel@vger.kernel.org References: <20030301043131.7D5301058@oscar.casa.dyndns.org> <20030301090839.GA11997@wotan.suse.de> In-Reply-To: <20030301090839.GA11997@wotan.suse.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200303010734.45441.tomlins@cam.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 858 Lines: 20 On March 1, 2003 04:08 am, Andi Kleen wrote: > > I wonder what would happen if you reordered the chains moving a 'found' > > dentry to the front of the chain? If this could be done without > > excessive locking it might help keep hot entries quickly accessable. > > This operation should be cheaper given you are using hlists. > > You would need to fetch a spinlock for LRU, while the current lookup > runs completely lockless. You would have to lock the chain IF the dentry was not at the head. Would be interesting to see if this locking would hurt much - since hot dentries would not require a lock... Ed - 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/