*BSD News Article 91530


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.Hawaii.Edu!news.caldera.com!enews.sgi.com!news.sgi.com!news1.best.com!nntp1.ba.best.com!not-for-mail
From: dillon@flea.best.net (Matt Dillon)
Newsgroups: comp.unix.bsd.freebsd.misc,comp.sys.sgi.misc
Subject: Re: no such thing as a "general user community"
Date: 20 Mar 1997 11:06:37 -0800
Organization: BEST Internet Communications, Inc.
Lines: 41
Message-ID: <5gs1rt$kel@flea.best.net>
References: <331BB7DD.28EC@net5.net> <5gmb58$6jd$1@news.clinet.fi> <5gn3ig$83d@flea.best.net> <333033B4.46AA@cet.co.jp>
NNTP-Posting-Host: flea.best.net
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37384 comp.sys.sgi.misc:29284

:In article <333033B4.46AA@cet.co.jp>,
:Michael Hancock  <michaelh@cet.co.jp> wrote:
:>Matt Dillon wrote:
:>
:>      As far as sensible SMP or filesystems 'like XFS' go.  I would
:>  like to point
:>      out that XFS has only very recently become stable, and only
:>  very, VERY
:>      recently has gotten a filesystem quota capability.  XFS's only
:>  performance
:>      advantage is in directory lookups.  It does not have any other
:>  advantage
:>      over FFS.  Filesystem locks and lockout conditions in XFS are
:>  barely
:>      on-par with the locking used in FFS in FreeBSD kernels (whereas
:>  in EFS the
:>      locks were substandard).  Furthermore, SGI treats RAID functions
:>  as
:>      extra-cost items, requiring a licence, rather then as native
:>  items.  And
:>      they aren't even that good.
:>
:>There was a suggestion to do name canonization on FBSD because it did a
:>lot of string copying of the path thru the VOP layers.  Namei/ufs_lookup
:>are pretty hairy, it might be worth it to redo these.
:>
:>Do you know how XFS does things?
:>
:>Regards,
:>
:>Mike Hancock

    Not having access to the xfs source, I can't say beyond what SGI tells
    me.

    As far as namei() string copies go... namei() has never really caused
    a cpu hogging issue.  The issue with namei() has always been with its
    caching.

					-Matt