I agree, does look quite useful. However, in the interests of backwards compatability, I would probably suggest adding a "-detailed" option or a new command name (fs getcacheinfo) as oppposed to just changing the output of getcacheparms.
-- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-6679 UMR Information Technology Fax: (573) 341-4216 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of chas > williams - CONTRACTOR > Sent: Wednesday, August 24, 2005 9:37 AM > To: Troy Benjegerdes > Cc: Jeffrey Hutzelman; openafs-devel@openafs.org > Subject: Re: [OpenAFS-devel] PATCH: limit afsd auto-tuning to > 500000 files > > In message <[EMAIL PROTECTED]>,Troy > Benjegerdes writes: > >>fs getcacheparms > >AFS using 64% of cache blocks (12751138 of 20000000 1k blocks) > > 2% of the cache files (8242 of 500000 files) > > this is really cool! a step in the right direction. can you also > compute/print out the average size of the cache files? a > short histogram > based on chunksizes (4k, 8k, 16k, ...CURRENT_CHUNKSIZE) would > be helpful > as well. this should help people decide which chunksize is "right" > for them. this would tend to make the histogram small enough to send > across the kernel/user space boundary. > _______________________________________________ > OpenAFS-devel mailing list > OpenAFS-devel@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-devel > > _______________________________________________ OpenAFS-devel mailing list OpenAFS-devel@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-devel
