1. 15 2月, 2007 1 次提交
    • T
      [PATCH] remove many unneeded #includes of sched.h · cd354f1a
      Tim Schmielau 提交于
      After Al Viro (finally) succeeded in removing the sched.h #include in module.h
      recently, it makes sense again to remove other superfluous sched.h includes.
      There are quite a lot of files which include it but don't actually need
      anything defined in there.  Presumably these includes were once needed for
      macros that used to live in sched.h, but moved to other header files in the
      course of cleaning it up.
      
      To ease the pain, this time I did not fiddle with any header files and only
      removed #includes from .c-files, which tend to cause less trouble.
      
      Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
      arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
      allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
      configs in arch/arm/configs on arm.  I also checked that no new warnings were
      introduced by the patch (actually, some warnings are removed that were emitted
      by unnecessarily included header files).
      Signed-off-by: NTim Schmielau <tim@physik3.uni-rostock.de>
      Acked-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cd354f1a
  2. 10 2月, 2007 1 次提交
  3. 06 2月, 2007 6 次提交
  4. 24 1月, 2007 2 次提交
  5. 22 11月, 2006 1 次提交
  6. 01 11月, 2006 1 次提交
  7. 05 10月, 2006 1 次提交
    • D
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells 提交于
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
      of passing regs around manually through all ~1800 interrupt handlers in the
      Linux kernel.
      
      The regs pointer is used in few places, but it potentially costs both stack
      space and code to pass it around.  On the FRV arch, removing the regs parameter
      from all the genirq function results in a 20% speed up of the IRQ exit path
      (ie: from leaving timer_interrupt() to leaving do_IRQ()).
      
      Where appropriate, an arch may override the generic storage facility and do
      something different with the variable.  On FRV, for instance, the address is
      maintained in GR28 at all times inside the kernel as part of general exception
      handling.
      
      Having looked over the code, it appears that the parameter may be handed down
      through up to twenty or so layers of functions.  Consider a USB character
      device attached to a USB hub, attached to a USB controller that posts its
      interrupts through a cascaded auxiliary interrupt controller.  A character
      device driver may want to pass regs to the sysrq handler through the input
      layer which adds another few layers of parameter passing.
      
      I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
      main part of the code on FRV and i386, though I can't test most of the drivers.
      I've also done partial conversion for powerpc and MIPS - these at least compile
      with minimal configurations.
      
      This will affect all archs.  Mostly the changes should be relatively easy.
      Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
      
      	struct pt_regs *old_regs = set_irq_regs(regs);
      
      And put the old one back at the end:
      
      	set_irq_regs(old_regs);
      
      Don't pass regs through to generic_handle_irq() or __do_IRQ().
      
      In timer_interrupt(), this sort of change will be necessary:
      
      	-	update_process_times(user_mode(regs));
      	-	profile_tick(CPU_PROFILING, regs);
      	+	update_process_times(user_mode(get_irq_regs()));
      	+	profile_tick(CPU_PROFILING);
      
      I'd like to move update_process_times()'s use of get_irq_regs() into itself,
      except that i386, alone of the archs, uses something other than user_mode().
      
      Some notes on the interrupt handling in the drivers:
      
       (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
           the input_dev struct.
      
       (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
           something different depending on whether it's been supplied with a regs
           pointer or not.
      
       (*) Various IRQ handler function pointers have been moved to type
           irq_handler_t.
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  8. 26 9月, 2006 2 次提交
  9. 23 9月, 2006 1 次提交
  10. 19 9月, 2006 1 次提交
  11. 14 9月, 2006 2 次提交
  12. 20 8月, 2006 2 次提交
  13. 04 8月, 2006 2 次提交
    • A
      [PATCH] s2io driver bug fixes #2 · 75c30b13
      Ananda Raju 提交于
      	This patch contains some of the bug fixes and enhancements done to
      	s2io driver. Following are the brief description of changes
      
      	1. code cleanup to handle gso modification better
      	2. Move repeated code in rx path, to a common function
      	   s2io_chk_rx_buffers()
      	3. Bug fix in MSI interrupt
      	4. clear statistics when card is down
      	5. Avoid linked list traversing in lro aggregation.
      	6. Use pci_dma_sync_single_for_cpu for buffer0 in case of 2/3
      	   buffer mode.
      	7. ethtool tso get/set functions to set clear NETIF_F_TSO6
      	8. Stop LRO aggregation when we receive ECN notification
      Signed-off-by: NAnanda Raju <ananda.raju@neterion.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      75c30b13
    • 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
  14. 13 7月, 2006 1 次提交
  15. 03 7月, 2006 1 次提交
  16. 01 7月, 2006 2 次提交
    • H
      [IPV6]: Added GSO support for TCPv6 · f83ef8c0
      Herbert Xu 提交于
      This patch adds GSO support for IPv6 and TCPv6.  This is based on a patch
      by Ananda Raju <Ananda.Raju@neterion.com>.  His original description is:
      
      	This patch enables TSO over IPv6. Currently Linux network stacks
      	restricts TSO over IPv6 by clearing of the NETIF_F_TSO bit from
      	"dev->features". This patch will remove this restriction.
      
      	This patch will introduce a new flag NETIF_F_TSO6 which will be used
      	to check whether device supports TSO over IPv6. If device support TSO
      	over IPv6 then we don't clear of NETIF_F_TSO and which will make the
      	TCP layer to create TSO packets. Any device supporting TSO over IPv6
      	will set NETIF_F_TSO6 flag in "dev->features" along with NETIF_F_TSO.
      
      	In case when user disables TSO using ethtool, NETIF_F_TSO will get
      	cleared from "dev->features". So even if we have NETIF_F_TSO6 we don't
      	get TSO packets created by TCP layer.
      
      	SKB_GSO_TCPV4 renamed to SKB_GSO_TCP to make it generic GSO packet.
      	SKB_GSO_UDPV4 renamed to SKB_GSO_UDP as UFO is not a IPv4 feature.
      	UFO is supported over IPv6 also
      
      	The following table shows there is significant improvement in
      	throughput with normal frames and CPU usage for both normal and jumbo.
      
      	--------------------------------------------------
      	|          |     1500        |      9600         |
      	|          ------------------|-------------------|
      	|          | thru     CPU    |  thru     CPU     |
      	--------------------------------------------------
      	| TSO OFF  | 2.00   5.5% id  |  5.66   20.0% id  |
      	--------------------------------------------------
      	| TSO ON   | 2.63   78.0 id  |  5.67   39.0% id  |
      	--------------------------------------------------
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f83ef8c0
    • J
      Remove obsolete #include <linux/config.h> · 6ab3d562
      Jörn Engel 提交于
      Signed-off-by: NJörn Engel <joern@wohnheim.fh-wedel.de>
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      6ab3d562
  17. 23 6月, 2006 1 次提交
    • H
      [NET]: Merge TSO/UFO fields in sk_buff · 7967168c
      Herbert Xu 提交于
      Having separate fields in sk_buff for TSO/UFO (tso_size/ufo_size) is not
      going to scale if we add any more segmentation methods (e.g., DCCP).  So
      let's merge them.
      
      They were used to tell the protocol of a packet.  This function has been
      subsumed by the new gso_type field.  This is essentially a set of netdev
      feature bits (shifted by 16 bits) that are required to process a specific
      skb.  As such it's easy to tell whether a given device can process a GSO
      skb: you just have to and the gso_type field and the netdev's features
      field.
      
      I've made gso_type a conjunction.  The idea is that you have a base type
      (e.g., SKB_GSO_TCPV4) that can be modified further to support new features.
      For example, if we add a hardware TSO type that supports ECN, they would
      declare NETIF_F_TSO | NETIF_F_TSO_ECN.  All TSO packets with CWR set would
      have a gso_type of SKB_GSO_TCPV4 | SKB_GSO_TCPV4_ECN while all other TSO
      packets would be SKB_GSO_TCPV4.  This means that only the CWR packets need
      to be emulated in software.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      7967168c
  18. 20 6月, 2006 1 次提交
  19. 24 5月, 2006 1 次提交
  20. 03 5月, 2006 5 次提交
    • A
      [PATCH] s2io: init/shutdown fixes · 5d3213cc
      Ananda Raju 提交于
      Hi,
      	The following patch contains fix related to init and shutdown of adapter
      	as per user guide.  The list of changes include
      
      	1. shutdown gracefully.
      	2. Need to mask/unmask interrupts in ISR required fro Xframe-E
      	3. Tx FIFO should be enabled after WRR calender programming
      Signed-off-by: NAnanda Raju <ananda.raju@neterion.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      5d3213cc
    • 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
    • A
      [PATCH] s2io: performance improvements · 863c11a9
      Ananda Raju 提交于
      hi,
      	This patch contains all the changes that were done to improve
      	performance of s2io driver. one line  description of the changes
      	are
      
      	1. For Non NAPI case the rx interrupt handler is being called
      	   unconditionally
      	2. code optimization and adding prefetch skb->data
      	3. Remove modulo operations in fast path
      	4. Enable Group Reads and set backoff interval to 0x1000
      	5. correct PIC_CNTL_SHARED_SPLITS  macro definition, and reduce
      	   pause parameter
      	6. Corrected logic of identifying rx buffer level in rx_buffer_level()
      	7. fix DMA map and unmap done with different sizes in 1-buf mode
      	8. Removed forcible disabling of ERO
      	9. Send up the packets with transfer code = 0x5
      Signed-off-by: NAnanda Raju <ananda.raju@neterion.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      863c11a9
  21. 05 3月, 2006 1 次提交
  22. 04 3月, 2006 1 次提交
  23. 07 2月, 2006 2 次提交
  24. 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