Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!batcomputer!itsgw!steinmetz!uunet!vsi!friedl
From: friedl@vsi.COM (Stephen J. Friedl)
Newsgroups: comp.unix.wizards
Subject: Re: System V file systems
Summary: 2K blocks in Sys V
Message-ID: <917@vsi.COM>
Date: 31 Oct 88 00:44:42 GMT
References: <6413@daver.UUCP> <8332@alice.UUCP> <1988Oct27.173247.2789@utzoo.uucp> <8338@rpp386.Dallas.TX.US>
Organization: V-Systems, Inc. -- Santa Ana, CA
Lines: 22

In article <8338@rpp386.Dallas.TX.US>, jfh@rpp386.Dallas.TX.US (The Beach Bum) writes:
> I have never seen a realistic benchmark [ multi-process, multi-file, random
> access ] validate the claims BSD FFS puts forward - except to the extent that
> having the larger block size dictates.  And soon USG Unix will have 2K blocks
> so expect that advantage to diminish.

These are available now.  System V Release 3.1.1 for the 3B15 has
had 2k blocks for some time, and Sys V Rel 3.2.1 for the 3B2 just
came out with it.

How hard is it for an instantiation of UNIX to support multiple
kinds of blocksizes?  I would think that keeping the blocksize in
the superblock would make it pretty easy, so I could use 1k blocks
for root, and (say) 8k for the /database partition with a dozen
files all > 1MB.  Currently it seems like a big deal for them
to come out with a new supported blocksize.

     Steve
-- 
Steve Friedl    V-Systems, Inc.  +1 714 545 6442    3B2-kind-of-guy
friedl@vsi.com     {backbones}!vsi.com!friedl    attmail!vsi!friedl
----Nancy Reagan on 120MB SCSI cartridge tape: "Just say *now*"----