From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 24 May 2002 13:04:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 24 May 2002 13:04:34 -0400 Received: from leibniz.math.psu.edu ([146.186.130.2]:30126 "EHLO math.psu.edu") by vger.kernel.org with ESMTP id ; Fri, 24 May 2002 13:04:34 -0400 Date: Fri, 24 May 2002 13:04:33 -0400 (EDT) From: Alexander Viro To: Andrea Arcangeli cc: Linus Torvalds , linux-kernel@vger.kernel.org Subject: Re: negative dentries wasting ram In-Reply-To: <20020524163942.GB15703@dualathlon.random> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 24 May 2002, Andrea Arcangeli wrote: > > Note that this will have to touch the FS anyway, since the O_CREAT thing > > forces a call down to the FS to actually create the file. > > yep. the only case where it could provide some in-core "caching" > positive effect is: > > unlink > open(w/o creat) > > but I don't see it as a common case. Guys, how about tracing the damn thing and checking what actually happens? Or, at least, checking the prototypes and noticing that ->create() takes (hashed) dentry as an argument, so if unlinked on had been freed we _must_ call ->lookup().