Skip to content
Snippets Groups Projects
  1. Jun 21, 2011
  2. Apr 27, 2011
  3. Mar 12, 2011
  4. Mar 03, 2011
  5. Feb 11, 2011
  6. Nov 16, 2010
    • John Fastabend's avatar
      ixgbe: DCB set PFC high and low water marks per data sheet specs · 16b61beb
      John Fastabend authored
      
      Currently the high and low water marks for PFC are being set
      conservatively for jumbo frames. This means the RX buffers
      are being underutilized in the default 1500 MTU. This patch
      fixes this so that the water marks are set as described in
      the data sheet considering the MTU size.
      
      The equation used is,
      
      RTT * 1.44 + MTU * 1.44 + MTU
      
      Where RTT is the round trip time and MTU is the max frame size
      in KB. To avoid floating point arithmetic FC_HIGH_WATER is
      defined
      
      ((((RTT + MTU) * 144) + 99) / 100) + MTU
      
      This changes how the hardware field fc.low_water and
      fc.high_water are used. With this change they are no longer
      storing the actual low water and high water markers but are
      storing the required head room in the buffer. This simplifies
      the logic and we do not need to account for the size of the
      buffer when setting the thresholds.
      
      Testing with iperf and 16 threads showed a slight uptick in
      throughput over a single traffic class .1-.2Gbps and a reduction
      in pause frames. Without the patch a 30 second run would show
      ~10-15 pause frames being transmitted with the patch ~2-5 are
      seen. Test were run back to back with 82599.
      
      Note RXPBSIZE is in KB and low and high water marks fields are
      also in KB. However the FCRT* registers are 32B granularity and
      right shifted 5 into the register,
      
      (((rx_pbsize - water_mark) * 1024) / 32) << 5
      
      is the most explicit conversion here we simplify
      
      (rx_pbsize - water_mark) * 32 << 5 = (rx_pbsize - water_mark) << 10
      
      This patch updates the PFC thresholds and legacy FC thresholds.
      
      Signed-off-by: default avatarJohn Fastabend <john.r.fastabend@intel.com>
      Tested-by: default avatarRoss Brattain <ross.b.brattain@intel.com>
      Signed-off-by: default avatarJeff Kirsher <jeffrey.t.kirsher@intel.com>
      16b61beb
  7. Oct 14, 2010
  8. Jan 13, 2010
  9. May 17, 2009
  10. Mar 26, 2009
  11. Feb 06, 2009
  12. Feb 01, 2009
  13. Dec 26, 2008
    • Hannes Eder's avatar
      drivers/net/ixgbe: fix sparse warnings: make symbols static · e855aac8
      Hannes Eder authored
      
      Fix this sparse warnings:
      
        drivers/net/ixgbe/ixgbe_82598.c:180:5: warning: symbol 'ixgbe_get_copper_link_capabilities_82598' was not declared. Should it be static?
        drivers/net/ixgbe/ixgbe_82598.c:245:5: warning: symbol 'ixgbe_setup_fc_82598' was not declared. Should it be static?
        drivers/net/ixgbe/ixgbe_82598.c:729:5: warning: symbol 'ixgbe_set_vmdq_82598' was not declared. Should it be static?
        drivers/net/ixgbe/ixgbe_82598.c:773:5: warning: symbol 'ixgbe_set_vfta_82598' was not declared. Should it be static?
        drivers/net/ixgbe/ixgbe_82598.c:897:5: warning: symbol 'ixgbe_read_analog_reg8_82598' was not declared. Should it be static?
        drivers/net/ixgbe/ixgbe_82598.c:919:5: warning: symbol 'ixgbe_write_analog_reg8_82598' was not declared. Should it be static?
        drivers/net/ixgbe/ixgbe_82598.c:940:5: warning: symbol 'ixgbe_read_i2c_eeprom_82598' was not declared. Should it be static?
        drivers/net/ixgbe/ixgbe_82598.c:1000:5: warning: symbol 'ixgbe_get_supported_physical_layer_82598' was not declared. Should it be static?
        drivers/net/ixgbe/ixgbe_dcb_82598.c:100:5: warning: symbol 'ixgbe_dcb_config_packet_buffers_82598' was not declared. Should it be static?
      
      Signed-off-by: default avatarHannes Eder <hannes@hanneseder.net>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      e855aac8
  14. Nov 20, 2008
Loading