Date: Thu, 29 Sep 2005 21:57:49 +0300 From: Giorgos Keramidas <keramida@linux.gr> To: Eric Anderson <anderson@centtech.com> Cc: freebsd-hackers@freebsd.org Subject: Re: ufsstat implementation Message-ID: <20050929185749.GB15714@flame.pc> In-Reply-To: <433C30AB.2030409@centtech.com> References: <433C30AB.2030409@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-09-29 13:21, Eric Anderson <anderson@centtech.com> wrote: > I've been looking at the ufs code, and thinking about wedging in some > statistic gathering pieces pretty much copied from the nfs code (and > nfsstat) to provide nearly the same functionality. > > I realize that adding statistic gathering code would techinically reduce > filesystem performance, so should I put a wrapper around the code pieces > checking a sysctl, or use #ifdef's around it, or neither? It would take running an implementation with and without ufsstats to see what the impact on filesystem performance is, so it seems to me the natural choise for early stages of development is an #ifdef that can easily be turned on/off and control where all of the code goes in or nothing at all :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050929185749.GB15714>