summaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/dlink/dl2k.c
diff options
context:
space:
mode:
authorMichael S. Tsirkin <mst@redhat.com>2012-12-03 11:07:14 +0100
committerDavid S. Miller <davem@davemloft.net>2012-12-03 21:07:36 +0100
commit5d097109257c03a71845729f8db6b5770c4bbedc (patch)
tree4ef14ea47b21f6f81412c95889ca30147e0f0458 /drivers/net/ethernet/dlink/dl2k.c
parentipv6: Make 'addrconf_rs_timer' send Router Solicitations (and re-arm itself) ... (diff)
downloadlinux-5d097109257c03a71845729f8db6b5770c4bbedc.tar.xz
linux-5d097109257c03a71845729f8db6b5770c4bbedc.zip
tun: only queue packets on device
Historically tun supported two modes of operation: - in default mode, a small number of packets would get queued at the device, the rest would be queued in qdisc - in one queue mode, all packets would get queued at the device This might have made sense up to a point where we made the queue depth for both modes the same and set it to a huge value (500) so unless the consumer is stuck the chance of losing packets is small. Thus in practice both modes behave the same, but the default mode has some problems: - if packets are never consumed, fragments are never orphaned which cases a DOS for sender using zero copy transmit - overrun errors are hard to diagnose: fifo error is incremented only once so you can not distinguish between userspace that is stuck and a transient failure, tcpdump on the device does not show any traffic Userspace solves this simply by enabling IFF_ONE_QUEUE but there seems to be little point in not doing the right thing for everyone, by default. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/dlink/dl2k.c')
0 files changed, 0 insertions, 0 deletions