1. 05 8月, 2014 1 次提交
    • K
      Drivers: net-next: hyperv: Increase the size of the sendbuf region · 06b47aac
      KY Srinivasan 提交于
      Intel did some benchmarking on our network throughput when Linux on Hyper-V
      is as used as a gateway. This fix gave us almost a 1 Gbps additional throughput
      on about 5Gbps base throughput we hadi, prior to increasing the sendbuf size.
      The sendbuf mechanism is a copy based transport that we have which is clearly
      more optimal than the copy-free page flipping mechanism (for small packets).
      In the forwarding scenario, we deal only with MTU sized packets,
      and increasing the size of the senbuf area gave us the additional performance.
      For what it is worth, Windows guests on Hyper-V, I am told use similar sendbuf
      size as well.
      
      The exact value of sendbuf I think is less important than the fact that it needs
      to be larger than what Linux can allocate as physically contiguous memory.
      Thus the change over to allocating via vmalloc().
      
      We currently allocate 16MB receive buffer and we use vmalloc there for allocation.
      Also the low level channel code has already been modified to deal with physically
      dis-contiguous memory in the ringbuffer setup.
      
      Based on experimentation Intel did, they say there was some improvement in throughput
      as the sendbuf size was increased up to 16MB and there was no effect on throughput
      beyond 16MB. Thus I have chosen 16MB here.
      
      Increasing the sendbuf value makes a material difference in small packet handling
      
      In this version of the patch, based on David's feedback, I have added
      additional details in the commit log.
      Signed-off-by: NK. Y. Srinivasan <kys@microsoft.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      06b47aac
  2. 24 7月, 2014 1 次提交
  3. 03 7月, 2014 1 次提交
  4. 17 6月, 2014 1 次提交
  5. 01 5月, 2014 1 次提交
    • K
      hyperv: Enable sendbuf mechanism on the send path · c25aaf81
      KY Srinivasan 提交于
      We send packets using a copy-free mechanism (this is the Guest to Host transport
      via VMBUS). While this is obviously optimal for large packets,
      it may not be optimal for small packets. Hyper-V host supports
      a second mechanism for sending packets that is "copy based". We implement that
      mechanism in this patch.
      
      In this version of the patch I have addressed a comment from David Miller.
      
      With this patch (and all of the other offload and VRSS patches), we are now able
      to almost saturate a 10G interface between Linux VMs on Hyper-V
      on different hosts - close to  9 Gbps as measured via iperf.
      Signed-off-by: NK. Y. Srinivasan <kys@microsoft.com>
      Reviewed-by: NHaiyang Zhang <haiyangz@microsoft.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c25aaf81
  6. 24 4月, 2014 2 次提交
  7. 22 4月, 2014 1 次提交
  8. 12 4月, 2014 1 次提交
  9. 11 3月, 2014 1 次提交
  10. 20 2月, 2014 1 次提交
  11. 18 2月, 2014 2 次提交
  12. 28 1月, 2014 1 次提交
  13. 07 12月, 2013 1 次提交
  14. 30 4月, 2013 1 次提交
  15. 09 4月, 2013 1 次提交
  16. 03 10月, 2012 2 次提交
  17. 04 8月, 2012 1 次提交
  18. 07 6月, 2012 1 次提交
  19. 05 6月, 2012 1 次提交
  20. 04 4月, 2012 1 次提交
  21. 13 3月, 2012 1 次提交
  22. 05 1月, 2012 3 次提交
  23. 10 12月, 2011 1 次提交
  24. 02 12月, 2011 1 次提交
  25. 29 11月, 2011 1 次提交
  26. 27 11月, 2011 1 次提交
  27. 17 9月, 2011 2 次提交
  28. 07 9月, 2011 5 次提交
  29. 30 8月, 2011 2 次提交