From owner-freebsd-fs@FreeBSD.ORG Thu Jul 31 23:37:08 2008 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 966E11065674 for ; Thu, 31 Jul 2008 23:37:08 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32703.mail.mud.yahoo.com (web32703.mail.mud.yahoo.com [68.142.207.247]) by mx1.freebsd.org (Postfix) with SMTP id 5943B8FC08 for ; Thu, 31 Jul 2008 23:37:08 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 56412 invoked by uid 60001); 31 Jul 2008 23:37:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=wgY6N+CXOLwg1d+Z+54OCMQjPvv4eVNzZiAn920Y1iaWlOKya5cea+VbV9YXSOhFh02Qq/VQk4IGYoGcGsBOHmD67UUbxTL2XmY83/fzAVCsA+i8tx73YCY3r4xM8e/f7afEyimscUVOdrdWy0uzSeZo/4m3shwmKS0dKMsyDwc=; Received: from [190.158.44.147] by web32703.mail.mud.yahoo.com via HTTP; Thu, 31 Jul 2008 16:37:07 PDT X-Mailer: YahooMailWebService/0.7.218 Date: Thu, 31 Jul 2008 16:37:07 -0700 (PDT) From: Pedro Giffuni To: freebsd-fs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID: <809288.56058.qm@web32703.mail.mud.yahoo.com> Cc: Subject: Should we change dirent for 64 bit directory cookies ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2008 23:37:08 -0000 Hello fs gurus; I've been sort of following the DragonFly list wrt to the changes Matt made= for his HAMMER fs. I don't know if anyone is considering a port: he added a lot of stuff to th= e base system that will be a pain to port, but he also triggered some bugs = in the old BSD code that would be nice to fix on FreeBSD too. One of the not-*too*-tough things to consider adopting would be 64 director= y cookies: Main commit: http://leaf.dragonflybsd.org/mailarchive/commits/2007-11/msg00151.html Follow up for the linuxulator: http://leaf.dragonflybsd.org/mailarchive/commits/2007-11/msg00153.html Here is a excerpt of a discussion from the DragonFly Kernel ML (Re: [Tux3] = Comparison to Hammer fs design), that pretty much sums up the issues: ________ ... :> The cookies are 64 bits in DragonFly. I'm not sure why Linux would :> still be using 32 bit cookies, file offsets are 64 bits so you :> should be able to use 64 bit cookies. : :It is not Linux that perpetrates this outrage, it is NVFS v2. We can't :just tell everybody that their NFS v2 clients are now broken. Oh, we don't care about NFSv2 all that much any more. NFSv3 is the bare minimum. NFSv2 is extremely old, nobody should be using it any more. Even NFSv3 is getting fairly long in the tooth now. :> For NFS in DragonFly I use a 64 bit cookie where 32 bits is a hash k= ey :> and 32 bits is an iterator to deal with hash collisions. Poof, :> problem solved. : :Which was my original proposal to solve the problem. Then Ted told me :about NFS v2 :-O : :Actually, NFS hands you a 62 bit cookie with the high bits of both s32 :parts unused. NFS v2 gives you a 31 bit cookie. Bleah. I'd recommend dropping support for NFSv2. It is not really worth=20 supporting any more. Does it even support 64 bit inodes? (I don't=20 remember), or 64 bit file offsets? NFSv2 is garbage. You should be able to use 63 bits of the cookie, I don't know why you wouldn't use the high bit of the lsb 32 bit part. There is no requirement that that bit be 0. In fact, the RFC says the cookie is a 64 bit unsigned integer and you should be able to use all 64 bits. If linux is not allowing all 64 bits to be used then it's a serious bug in linux. The cookies are supposed to be opaque, just like the file handle. ... _________ =0A=0A=0A Posta, news, sport, oroscopo: tutto in una sola pagina. =0AC= rea l'home page che piace a te!=0Awww.yahoo.it/latuapagina