00e7d35ef0
Bump the default values for these to the values used by FreeBSD, and also adjust ti_init_rx_ring_jumbo() to use the same constant that FreeBSD uses. Yes, this consumes more kernel memory. The effect of this is that you can use jumbo frames in a back-to-back setup with TCP windows up to about 250KB and get ~930Mbit/s throughput, while we were earlier limited to around 3-400Mbit/s, and trying to push above that mark by widening the TCP window caused ti0: jumbo buffer allocation failed messages to be logged and a corresponding stall in the traffic.