summaryrefslogtreecommitdiff
path: root/drivers/net/dummy.c
diff options
context:
space:
mode:
authorJuergen Gross <jgross@suse.com>2018-06-12 09:57:53 +0300
committerDavid S. Miller <davem@davemloft.net>2018-06-13 01:42:38 +0300
commit57f230ab04d2910a06d17d988f1c4d7586a59113 (patch)
treec11ba9e13cf34a683fe4721442e7914c4e234965 /drivers/net/dummy.c
parentc0129a0614428e5e4350fa963eecd1fbe19e57e9 (diff)
downloadlinux-57f230ab04d2910a06d17d988f1c4d7586a59113.tar.xz
xen/netfront: raise max number of slots in xennet_get_responses()
The max number of slots used in xennet_get_responses() is set to MAX_SKB_FRAGS + (rx->status <= RX_COPY_THRESHOLD). In old kernel-xen MAX_SKB_FRAGS was 18, while nowadays it is 17. This difference is resulting in frequent messages "too many slots" and a reduced network throughput for some workloads (factor 10 below that of a kernel-xen based guest). Replacing MAX_SKB_FRAGS by XEN_NETIF_NR_SLOTS_MIN for calculation of the max number of slots to use solves that problem (tests showed no more messages "too many slots" and throughput was as high as with the kernel-xen based guest system). Replace MAX_SKB_FRAGS-2 by XEN_NETIF_NR_SLOTS_MIN-1 in netfront_tx_slot_available() for making it clearer what is really being tested without actually modifying the tested value. Signed-off-by: Juergen Gross <jgross@suse.com> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/dummy.c')
0 files changed, 0 insertions, 0 deletions