busdma: On systmes that use subr_busdma_bounce, measure deferred time

[imp]

Summary

Measure the total deferred time (from the time we decide to defer until
we try again) for busdma_load requests. On systems that don't ever
defer, there is no performnce change. Add new sysctl
hw.busdma.zoneX.total_deferred_time to report this (in
microseconds).

Normally, deferrals don't happen in modern hardware... Except there's a
lot of buggy hardware that can't cope with memory > 4GB or that can't
cross a 4GB boundary (or even more restrictive values), necessitating
bouncing. This will measure the effect on the I/Os of this deferral.

Sponsored by: Netflix

[mav]

It looks OK to me, except getsbinuptime() by default gives a millisecond precision, not microsecond. Not a huge deal probably. Should average over time if it happen often.

[imp]

In D42550#970845, @mav wrote:

It looks OK to me, except getsbinuptime() by default gives a millisecond precision, not microsecond. Not a huge deal probably. Should average over time if it happen often.

I think I got getsinuptime and sbinuptime confused...