On Tue, Jul 29, 2008 at 6:13 AM, Gerrit Renker <gerrit@xxxxxxxxxxxxxx> wrote: > > This prevents module loading when the timer resolution is too low > (e.g. when using jiffies as a clocksource or when disabling high > resolution timers on sparc64). > > Rationale: > ---------- > The DCCP base time resolution is 10 microseconds (RFC 4340, 13.1...3). Using a > timer with a lower resolution than that was found to trigger the following bug > warnings/problems on high-speed networks (e.g. local loopback): > > * small RTT samples are rounded down to 0 > (in some cases, even negative RTT samples occurred); > * the CCID-3 feedback timer complains that the feedback interval is 0, > since the coarse-grained resolution rounds RTT-wise intervals down. > > The following syslog messages were observed with a low resolution: > 11:24:00 kernel: BUG: delta (0) <= 0 at ccid3_hc_rx_send_feedback() > 11:26:12 kernel: BUG: delta (0) <= 0 at ccid3_hc_rx_send_feedback() > 11:26:30 kernel: dccp_sample_rtt: unusable RTT sample 0, using min > 11:26:30 last message repeated 5 times > > Signed-off-by: Gerrit Renker <gerrit@xxxxxxxxxxxxxx> I don't think this is the right direction to head. I think it is acceptable to have not perfect performance if HR timers aren't loaded (and I'm sure ways could be made to improve this) but to disable CCID3 altogether is quite drastic. Where will CCID3 be used - think embedded multimedia home devices. These may not have HR timers.... So I disagree with this one. Ian -- To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
