From owner-freebsd-afs Sat May 5 17:27:47 2001 Delivered-To: freebsd-afs@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id DEB7637B423 for ; Sat, 5 May 2001 17:27:44 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f460R3f27587; Sat, 5 May 2001 20:27:03 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 5 May 2001 20:27:03 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Johan Danielsson Cc: Mitch Collinsworth , Tom Maher , freebsd-afs@FreeBSD.ORG, port-freebsd@openafs.org Subject: Re: [OpenAFS-port-freebsd] Re: afs port In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-afs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 31 Mar 2001, Johan Danielsson wrote: > > I don't know the internals enough to answer that, but judging from > > the AFS Installation Guide, the kernel mods are pre-requisite to > > running the server processes. > > That's because the fileserver uses special system calls to bypass the > ufs namespace when allocating files. Any first, sane, implementation > should probably go the linux way and circumvent this problem. Another thing that would be very interesting to look at is using IFS for client and server file storage: IFS is a subset of FFS done by Adrian Chad . What IFS does is use inode numbers to provide a single directory namespace in the root of the fs, removing the requirement that expensive synchronous namespace operations occur, allowing the application to provide these meta-data services itself. He did the work specifically with Squid in mind, but it could easily be adapted for use under OpenAFS or Coda. At least on the server, this would remove the requirement for special kernel code, as low-cost file store services would be available in userland. The client would continue to need a kernel module, but container files could likewise be stored in an IFS file system. Of course, if this is used, it would be interesting to compare the performance results with IFS and the performance results of using the kernel module for the server. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-afs" in the body of the message