1. 04 8月, 2006 1 次提交
    • A
      [PATCH] s2io driver bug fixes #1 · b41477f3
      Ananda Raju 提交于
      	This patch contains some of the bug fixes and enhancements done to
      	s2io driver. Following are the brief description of changes
      
      	1. Introduced macro "S2IO_PARM_INT" for declaring integer load parameter
      	2. UDP_RR test failure, memset txdl after Tx completion
      	3. PXE boot may leave adapter in unknown state so do reset in probe.
      	4. Add Tx completion code in netpoll
      	5. In s2io_vpd_read() move array vpd_data[] to pointer, saves stack memory
      	6. Fix bug in ethtool online test
      Signed-off-by: NAnanda Raju <ananda.raju@neterion.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      b41477f3
  2. 13 7月, 2006 1 次提交
  3. 01 7月, 2006 1 次提交
  4. 03 5月, 2006 3 次提交
    • A
      [PATCH] s2io: additional stats · bd1034f0
      Ananda Raju 提交于
      Hi,
      	This patch contains additional statistics counters added to s2io driver
      	these statistics are very much usefull in debugging the driver.
      Signed-off-by: NAnanda Raju <ananda.raju@neterion.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      bd1034f0
    • A
      [PATCH] s2io: fixes · c92ca04b
      Ananda Raju 提交于
      Hi,
      	This patch contains some of the bug fixes done for S2io driver.
      	Following are the brief description of changes
      
      	1. Continuing with initialization if we get minimum required MSI-X vectors
      	2. fix for ethtool online link test fails
      	3. make wait_for_cmd_complete generic for all command status registers
      	4. Print "Device is on PCI-E bus" for Xframe-E card
      	5. CX4 requires additional delay after sw_reset, and requires higher value for igp
      	6. Fixed panic due to non-TCP and/or LLC/SNAP traffic in case of lro
      	7. remove legacy code for old transponder
      	8. SPECIAL_REG_WRITE made to use 32-bit writes irrespective of system type
      	9. handle link interrupt as per user guide for Xframe II
      	10. Wait till all interrupts hndled
      Signed-off-by: NAnanda Raju <ananda.raju@neterion.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      c92ca04b
    • A
      [PATCH] s2io: input parms, output messages update · 9dc737a7
      Ananda Raju 提交于
      hi,
      	This patch contains the modification and bug fixes with respect to
      	input parameters and outupt dmesages. following is brief description
      	of the changes.
      
      	1. Set default values for rx_ring_sz[0..7] and tx_fifo_len[0..7]
      	2. verify few basic load parameters
      	3. read product description from VPD
      	4. clean up of dmesg  when driver is loaded
      Signed-off-by: NAnanda Raju <ananda.raju@neterion.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      9dc737a7
  5. 27 1月, 2006 1 次提交
    • R
      [PATCH] S2io: Large Receive Offload (LRO) feature(v2) for Neterion (s2io)... · 7d3d0439
      Ravinandan Arakali 提交于
      [PATCH] S2io: Large Receive Offload (LRO) feature(v2) for Neterion (s2io) 10GbE Xframe PCI-X and PCI-E NICs
      
      Hi,
      Below is a patch for the Large Receive Offload feature.
      Please review and let us know your comments.
      
      LRO algorithm was described in an OLS 2005 presentation, located at
      ftp.s2io.com
      user: linuxdocs
      password: HALdocs
      
      The same ftp site has Programming Manual for Xframe-I ASIC.
      LRO feature is supported on Neterion Xframe-I, Xframe-II and
      Xframe-Express 10GbE NICs.
      
      Brief description:
      The Large Receive Offload(LRO) feature is a stateless offload
      that is complementary to TSO feature but on the receive path.
      The idea is to combine and collapse(upto 64K maximum) in the
      driver, in-sequence TCP packets belonging to the same session.
      It is mainly designed to improve 1500 mtu receive performance,
      since Jumbo frame performance is already close to 10GbE line
      rate. Some performance numbers are attached below.
      
      Implementation details:
      1. Handle packet chains from multiple sessions(current default
      MAX_LRO_SESSSIONS=32).
      2. Examine each packet for eligiblity to aggregate. A packet is
      considered eligible if it meets all the below criteria.
        a. It is a TCP/IP packet and L2 type is not LLC or SNAP.
        b. The packet has no checksum errors(L3 and L4).
        c. There are no IP options. The only TCP option supported is timestamps.
        d. Search and locate the LRO object corresponding to this
           socket and ensure packet is in TCP sequence.
        e. It's not a special packet(SYN, FIN, RST, URG, PSH etc. flags are not set).
        f. TCP payload is non-zero(It's not a pure ACK).
        g. It's not an IP-fragmented packet.
      3. If a packet is found eligible, the LRO object is updated with
         information such as next sequence number expected, current length
         of aggregated packet and so on. If not eligible or max packets
         reached, update IP and TCP headers of first packet in the chain
         and pass it up to stack.
      4. The frag_list in skb structure is used to chain packets into one
         large packet.
      
      Kernel changes required: None
      
      Performance results:
      Main focus of the initial testing was on 1500 mtu receiver, since this
      is a bottleneck not covered by the existing stateless offloads.
      
      There are couple disclaimers about the performance results below:
      1. Your mileage will vary!!!! We initially concentrated on couple pci-x
      2.0 platforms that are powerful enough to push 10 GbE NIC and do not
      have bottlenecks other than cpu%;  testing on other platforms is still
      in progress. On some lower end systems we are seeing lower gains.
      
      2. Current LRO implementation is still (for the most part) software based,
      and therefore performance potential of the feature is far from being realized.
      Full hw implementation of LRO is expected in the next version of Xframe ASIC.
      
      Performance delta(with MTU=1500) going from LRO disabled to enabled:
      IBM 2-way Xeon (x366) : 3.5 to 7.1 Gbps
      2-way Opteron : 4.5 to 6.1 Gbps
      Signed-off-by: NRavinandan Arakali <ravinandan.arakali@neterion.com>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      7d3d0439
  6. 17 1月, 2006 1 次提交
  7. 19 11月, 2005 1 次提交
  8. 06 11月, 2005 1 次提交
    • A
      [PATCH] S2io: Multi buffer mode support · da6971d8
      Ananda Raju 提交于
      Hi,
      This patch  provides dynamic two buffer-mode and 3 buffer-mode options.
      Previously 2 buffer-mode was compilation option. Now with this patch applied
      one can load driver in 2 buffer-mode with module-load parameter
      
      ie.
      #insmod s2io.ko rx_ring_mode=2
      
      This patch also provides 3 buffer-mode which provides header separation
      functionality. In 3 buffer-mode skb->data will have L2/L3/L4 headers and
      "skb_shinfo(skb)->frag_list->data" will have have L4 payload.
      one can load driver in 3 buffer-mode with same above module-load parameter
      
      ie.
      #insmod s2io.ko rx_ring_mode=3
      
      Please review the patch.
      Signed-off-by: NAnanda Raju <ananda.raju@neterion.com>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      da6971d8
  9. 04 10月, 2005 1 次提交
  10. 07 9月, 2005 1 次提交
    • R
      [PATCH] S2io: Hardware and miscellaneous fixes · 776bd20f
      ravinandan.arakali@neterion.com 提交于
      Hi,
      This patch contains the following hardware related fixes and other
      miscellaneous bug fixes.
      
      1. Updated the definition of single and double-bit ECC errors
      2. Earlier we were allocating Transmit descriptors equal to
         MAX_SKB_FRAGS. This was causing a boundary condition failure.
         Need to allocate MAX_SKB_FRAGS+1 descriptors.
      3. On some platforms(like PPC), pci_alloc_consistent() can return
         a zero DMA address. Since the NIC cannot handle zero-addresses,
         a workaround has been provided. Basically, we don't use such
         that page. We reallocate.
      4. If list_info allocation failed during driver load, check for
         it during driver exit and return instead of trying to dereference
         NULL pointer.
      5. Increase the debug level of few non-critical debug messages.
      6. Reset the card on critical ECC double errors only in case of
         XframeI since XframeII can recover from such errors.
      7. Print copyright message on driver load.
      8. Bumped up the driver version no. to 2.0.8.1
      Signed-off-by: NRavinandan Arakali <ravinandan.arakali@neterion.com>
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      776bd20f
  11. 30 8月, 2005 1 次提交
  12. 11 8月, 2005 9 次提交
  13. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4