summaryrefslogtreecommitdiffstats
path: root/sys/kern/subr_bus.c
diff options
context:
space:
mode:
authorrrs <rrs@FreeBSD.org>2010-06-07 18:29:10 +0000
committerrrs <rrs@FreeBSD.org>2010-06-07 18:29:10 +0000
commit79f1540a6e376aeac8e821beeeed9ee73efe6068 (patch)
treec26e4903dcf57375a51425764f25a74d00b5a4c8 /sys/kern/subr_bus.c
parentde50224e92852178751a81d47695249fc681acd0 (diff)
downloadFreeBSD-src-79f1540a6e376aeac8e821beeeed9ee73efe6068.zip
FreeBSD-src-79f1540a6e376aeac8e821beeeed9ee73efe6068.tar.gz
This fixes a BUG in the handling of the cum-ack calculation.
We were only paying attention to the nr-mapping-array. Which seems to make sense on the surface, by definition things up to the cum-ack should be deliverable thus in the nr-mapping-array. However (there is always a gotcha) thats not true when it comes to large messages. The stack may hold the message while re-assembling it not not deliver it based on several thresholds. If that happens (which it would for smaller large messages) then the cum-ack is figured wrong. We now properly use both arrays in the cum-ack calculation. MFC after: 1 week.
Diffstat (limited to 'sys/kern/subr_bus.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud