This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Wed Apr 24 22:52:04 2024 Received: from lml.valinux.com (postfix@lml.valinux.com [198.186.203.19]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id PAA16716 for ; Mon, 6 Mar 2000 15:47:20 -0500 (EST) Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by lml.valinux.com (Postfix) with ESMTP id B1C4C5AA22; Mon, 6 Mar 2000 12:47:08 -0800 (PST) Received: by vger.rutgers.edu via listexpand id ; Mon, 6 Mar 2000 11:20:29 -0500 Received: by vger.rutgers.edu id ; Mon, 6 Mar 2000 10:47:14 -0500 Received: from idiom.com ([216.240.32.1]:3583 "EHLO idiom.com") by vger.rutgers.edu with ESMTP id ; Mon, 6 Mar 2000 10:45:02 -0500 Received: from idiom.com (reiser.dial.idiom.com [216.240.37.24]) by idiom.com (8.9.3/8.9.3) with ESMTP id LAA31231; Mon, 6 Mar 2000 11:44:40 -0800 (PST) Message-Id: <38C371B5.C48EBB05@idiom.com> Date: Mon, 06 Mar 2000 11:52:05 +0300 From: Hans Reiser X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i686) X-Accept-Language: en, ru Mime-Version: 1.0 To: Jamie Lokier Cc: Alexander Viro , "linux-kernel@vger.rutgers.edu" , "linux-fsdevel@vger.rutgers.edu`" Subject: Re: Does your change make find faster by changing where it is storedor where it is returned? References: <38C2DAC2.7713713B@idiom.com> <20000306142741.F4819@pcep-jamie.cern.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig Let me be careful here, are you saying then that you got a 2x speedup by not changing where it was stored and only changing where it was returned, and thereby reducing syscall overhead? Hans Jamie Lokier wrote: > The file type is already stored in the directory for all filesystems > that say "FULL SUPPORT".  > > The patch changes where it is returned -- by not having to call stat(), > the inode is not read from disk. As a bonus you reduce inode cache > thrashing. > > For filesystems that store the inode in the directory itself, there is > no saving in I/O. > You may as well return the type info anyway because > it reduces kernel inode cache thrashing and reduces the number of > syscalls. > > enjoy, > -- Jamie -- You can get ReiserFS at http://devlinux.org/namesys, and customizations and industrial grade support at reiser@idiom.com. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/