> As for the other eight percent, I'm convinced that the jumper is adding
> another wait state when it's set to 33.  This is consistent with HPs very
> conservative (read: solid) designs.  But I wouldn't have thought that this
> would affect context switch times so much more than the dhrystones
> benchmark.  I guess the dhrystones benchmark is hanging out in the 040
> on-chip caches while ctxsig is requiring off-chip memory accesses.
> 
Are you sure that this jumper is not affecting the clock rate (like making
it run slow)?  That is, you verified that the elapsed time reported by
the CPU was consistant with "real time"?

I would think that it is independent of that but you never know...