>
> > Btw, I sure wish someone would comment on the S_LOCK analysis even if only
> > to tell me not to make such long posts as it wastes bandwidth. Or
> > was it just too long to read?
>
> I read it all! Great analysis of the situation and not a waste, IMHO.
>
> One comment...when you ran the tests in succession, could the cache be
> responsible for the timing groupings in the same test? Should a
> little program be run in between to "flush" the cache full of garbage
> so each real run will miss? Seem to recall a little program, in CUJ,
> I think, that set up a big array and then iterated over it to trash
> the cache.
Yes, that is a good point. When testing in a loop, the function is in
the cache, while in normal use, the function may not be in the cache
because of intervening instructions.
--
Bruce Momjian | 830 Blythe Avenue
maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
