1. 09 3月, 2015 1 次提交
  2. 07 3月, 2015 3 次提交
  3. 03 3月, 2015 1 次提交
  4. 26 2月, 2015 3 次提交
  5. 24 2月, 2015 1 次提交
    • M
      i40e/i40evf: Refactor the receive routines · a132af24
      Mitch Williams 提交于
      Split the receive hot path code into two, one for packet split and one
      for single buffer. This improves receive performance since we only need
      to check if the ring is in packet split mode once per NAPI poll time,
      not several times per packet. The single buffer code is further improved
      by the removal of a bunch of code and several variables that are not
      needed. On a receive-oriented test this can improve single-threaded
      throughput.
      
      Also refactor the packet split receive path to use a fixed buffer for
      headers, like ixgbe does. This vastly reduces the number of DMA mappings
      and unmappings we need to do, allowing for much better performance in
      the presence of an IOMMU.
      
      Lastly, correct packet split descriptor types now that we are actually
      using them.
      
      Change-ID: I3a194a93af3d2c31e77ff17644ac7376da6f3e4b
      Signed-off-by: NMitch Williams <mitch.a.williams@intel.com>
      Tested-by: NJim Young <james.m.young@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      a132af24
  6. 10 2月, 2015 1 次提交
  7. 09 2月, 2015 2 次提交
  8. 14 1月, 2015 1 次提交
  9. 30 8月, 2014 1 次提交
  10. 27 8月, 2014 1 次提交
  11. 26 8月, 2014 1 次提交
    • V
      i40evf: Fix TSO and hw checksums for non-accelerated vlan packets. · a12c4158
      Vlad Yasevich 提交于
      This device claims TSO and checksum support for vlans.  It also
      allows a user to control vlan acceleration offloading.  As such,
      it is possible to turn off vlan acceleration and configure a vlan
      which will continue to support TSO and hw checksums.
      
      In such situation the packet passed down the the device will contain
      a vlan header and skb->protocol will be set to ETH_P_8021Q.
      The device assumes that skb->protocol contains network protocol
      value and uses that value to set up TSO and checksum information.
      This results in corrupted frames sent on the wire.
      
      This patch extract the protocol value correctly and corrects TSO
      and checksums for non-accelerated traffic.
      
      Fix this by using vlan_get_protocol() helper.
      
      CC: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
      CC: Jesse Brandeburg <jesse.brandeburg@intel.com>
      CC: Bruce Allan <bruce.w.allan@intel.com>
      CC: Carolyn Wyborny <carolyn.wyborny@intel.com>
      CC: Don Skidmore <donald.c.skidmore@intel.com>
      CC: Greg Rose <gregory.v.rose@intel.com>
      CC: Alex Duyck <alexander.h.duyck@intel.com>
      CC: John Ronciak <john.ronciak@intel.com>
      CC: Mitch Williams <mitch.a.williams@intel.com>
      CC: Linux NICS <linux.nics@intel.com>
      CC: e1000-devel@lists.sourceforge.net
      Signed-off-by: NVladislav Yasevich <vyasevic@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a12c4158
  12. 24 7月, 2014 1 次提交
  13. 03 7月, 2014 1 次提交
  14. 01 7月, 2014 1 次提交
  15. 09 6月, 2014 1 次提交
  16. 08 6月, 2014 1 次提交
    • J
      i40e/i40evf: fix TSO accounting · 980093eb
      Jesse Brandeburg 提交于
      The TSO logic in the transmit path had some assumptions that
      have been broken now that the kernel can send as much as 32kB
      in a single skb->frag[.] entry, even on a system with 4kB pages.
      
      This fixes the assumptions and allows the kernel to operate
      as efficiently as possible with both SENDFILE and SEND.
      
      In addition, the hardware limit of data contained in a descriptor is
      changed to the next power of two below where it currently is in
      order to align to a power of two value, preventing a single byte
      of data in a descriptor.
      
      Change-ID: I6af1f0b87c1458e10644dbd47541591075a52651
      Signed-off-by: NJesse Brandeburg <jesse.brandeburg@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      980093eb
  17. 21 5月, 2014 1 次提交
  18. 11 4月, 2014 1 次提交
  19. 20 3月, 2014 2 次提交
  20. 07 3月, 2014 2 次提交
  21. 14 2月, 2014 2 次提交
  22. 11 1月, 2014 1 次提交
  23. 01 1月, 2014 1 次提交
  24. 07 12月, 2013 1 次提交
  25. 22 10月, 2013 4 次提交
  26. 10 10月, 2013 4 次提交