From owner-freebsd-fs Thu Apr 24 17:01:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA10796 for fs-outgoing; Thu, 24 Apr 1997 17:01:42 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA10791 for ; Thu, 24 Apr 1997 17:01:40 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id RAA11911; Thu, 24 Apr 1997 17:03:00 -0700 (PDT) Message-Id: <199704250003.RAA11911@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Don Lewis cc: fs@freebsd.org Subject: Re: the namei cache... In-reply-to: Your message of "Thu, 24 Apr 1997 16:56:18 PDT." <199704242356.QAA12777@salsa.gv.tsc.tdk.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 24 Apr 1997 17:03:00 -0700 Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Apr 24, 8:24pm, Narvi wrote: >} Subject: Re: the namei cache... >} >} How about not adding byte values but say, long values? We may have to keep >} upto 3 bytes of additional space (avoiding overuns) but get it done in >} about 1/4th of the additions. > >The additions are pretty cheap. The problem with adding bigger chunks is >that the names aren't word aligned, so for each set of 4 bytes, you have >to read two words, extract the desired bytes, and concatenate the results. Actually, you could read/add in 16bit words since the component name is null terminated...or if the trailing space is zeroed up to a longword boundry, you could add in longwords. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project