Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 13 Jul 2002 13:48:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 13 Jul 2002 13:48:50 -0400 Received: from gateway2.ensim.com ([65.164.64.250]:55561 "EHLO nasdaq.ms.ensim.com") by vger.kernel.org with ESMTP id ; Sat, 13 Jul 2002 13:48:50 -0400 X-Mailer: exmh version 2.5 01/15/2001 with nmh-1.0.4 From: Paul Menage To: Alexander Viro cc: LKML , lse-tech Subject: Re: [Lse-tech] Re: [RFC] dcache scalability patch (2.4.17) cc: pmenage@ensim.com In-reply-to: Your message of "Sat, 13 Jul 2002 13:33:10 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Jul 2002 10:51:10 -0700 Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1125 Lines: 29 > > >On Sat, 13 Jul 2002, Paul Menage wrote: > >> - accessing foo/../bar, won't mark foo as referenced, even though it >> might be being referenced frequently. Probably not a common case for foo >> to be accessed exclusively in this way, but it could be fixed by marking >> a dentry referenced when following ".." > >It certainly will. Look - until ->d_count hits zero referenced bit is >not touched or looked at. At all. > >Look at the code. There is _no_ aging for dentries with positive ->d_count. >They start aging only when after they enter unused_list... > Yes, but with the fastwalk lookup, accessing foo/../bar won't do a dget() for foo (assuming it was cached), and hence will never do a dput() on it either. So if the only references to foo are as foo/../bar then its d_count will stay zero and it will never be marked referenced. (Or am I missing something?) Paul - 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/