From mboxrd@z Thu Jan 1 00:00:00 1970 From: kewlemer Subject: namei.c Date: Fri, 29 Apr 2005 02:09:55 -0700 Message-ID: <79cbe675050429020925edadbf@mail.gmail.com> Reply-To: kewlemer Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: from zproxy.gmail.com ([64.233.162.203]:48768 "EHLO zproxy.gmail.com") by vger.kernel.org with ESMTP id S262479AbVD2JJ5 convert rfc822-to-8bit (ORCPT ); Fri, 29 Apr 2005 05:09:57 -0400 Received: by zproxy.gmail.com with SMTP id 18so962068nzp for ; Fri, 29 Apr 2005 02:09:55 -0700 (PDT) To: linux-fsdevel@vger.kernel.org Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org I know that this group is for serious file system development discussion and I am hoping anyone of you will spare a few minutes to answer my trivial question. I am a grad student trying to port a ext3 COW utility from 2.4 to 2.6. One of the major changes I see in the 2.6 ext3 is the use of dx_ functions. Looking the source code, I understand that some kind of hashing is being done in these functions. It would be great if anyone can tell me whats is the basic idea behind these dx_ functions. General pointers on changes to ext3 in 2.6 will be greatly appreciated. Thanks! KM