right, the UBC code doesn't print anything during the boot process.

the way to tell that it's there is to do a bunch of file access
that didn't fit in the cache before but that does fit now.
the amount of memory available for cached file data under UBC is
currently about 85% of the amount listed in the "avail memory = X" line.

another way to tell that it's there is to access data via both
read()/write() and via mmap() and see that these two interfaces
to the filesystem now return the same data, whereas before
you'd see cache incoherency.  I've put a program to demonstrate
this named "vmtest.c" in the same directory with the diffs.

-Chuck


On Sun, Nov 05, 2000 at 08:50:59AM -0500, Joseph Sarkes wrote:
> Well, I installed the patch, and rebuild the kernel and the
> source tree. My system is running, but how can I tell the
> difference from before? I was running with about 25% memory
> set to buffers before, and now the systat/bufcache shows 13Mb
> buffers which is back to the default 5%. Is the ubc running
> with no indications? or do I have to enable it in the config
> file somehow? No documentation comes up with apropos or man.
> 
> If it IS running now, at least my system is running, which is
> a plus datapoint... running todays -current vice when the patch
> was made a few days ago with no probs. Still some indication in
> the startup messages or something would help, as all I really 
> see is the old messages.
> 
> -- 
> Joseph Sarkes		jsarkes@tiac.net