1. 07 6月, 2012 1 次提交
  2. 18 5月, 2012 1 次提交
    • P
      drivers/net: delete all code/drivers depending on CONFIG_MCA · a5e371f6
      Paul Gortmaker 提交于
      The support for CONFIG_MCA is being removed, since the 20
      year old hardware simply isn't capable of meeting today's
      software demands on CPU and memory resources.
      
      This commit removes any MCA specific net drivers, and removes
      any MCA specific probe/support code from drivers that were
      doing a dual ISA/MCA role.
      
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
      Cc: netdev@vger.kernel.org
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      a5e371f6
  3. 17 5月, 2012 1 次提交
  4. 16 5月, 2012 1 次提交
    • P
      tokenring: delete all remaining driver support · ee446fd5
      Paul Gortmaker 提交于
      This represents the mass deletion of the of the tokenring support.
      
      It gets rid of:
        - the net/tr.c which the drivers depended on
        - the drivers/net component
        - the Kbuild infrastructure around it
        - any tokenring related CONFIG_ settings in any defconfigs
        - the tokenring headers in the include/linux dir
        - the firmware associated with the tokenring drivers.
        - any associated token ring documentation.
      Signed-off-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      ee446fd5
  5. 14 5月, 2012 1 次提交
    • S
      batman-adv: README cleanups · a77e8c61
      Sven Eckelmann 提交于
      - Add routing_algo
      
      - Remove date from README:
      The date has to be updated when a patch touches the README. Therefore, nearly
      every feature will modify this date. It can happens quite often that not only
      one feature is currently in development or waiting on the mailinglist. This
      creates merge conflicts when applying a patchset.
      
      The date itself doesn't provide any additional information when this file is
      only available in a release tarball or as part of a SCM repository.
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
      a77e8c61
  6. 09 5月, 2012 1 次提交
  7. 03 5月, 2012 2 次提交
    • E
      tcp: change tcp_adv_win_scale and tcp_rmem[2] · b49960a0
      Eric Dumazet 提交于
      tcp_adv_win_scale default value is 2, meaning we expect a good citizen
      skb to have skb->len / skb->truesize ratio of 75% (3/4)
      
      In 2.6 kernels we (mis)accounted for typical MSS=1460 frame :
      1536 + 64 + 256 = 1856 'estimated truesize', and 1856 * 3/4 = 1392.
      So these skbs were considered as not bloated.
      
      With recent truesize fixes, a typical MSS=1460 frame truesize is now the
      more precise :
      2048 + 256 = 2304. But 2304 * 3/4 = 1728.
      So these skb are not good citizen anymore, because 1460 < 1728
      
      (GRO can escape this problem because it build skbs with a too low
      truesize.)
      
      This also means tcp advertises a too optimistic window for a given
      allocated rcvspace : When receiving frames, sk_rmem_alloc can hit
      sk_rcvbuf limit and we call tcp_prune_queue()/tcp_collapse() too often,
      especially when application is slow to drain its receive queue or in
      case of losses (netperf is fast, scp is slow). This is a major latency
      source.
      
      We should adjust the len/truesize ratio to 50% instead of 75%
      
      This patch :
      
      1) changes tcp_adv_win_scale default to 1 instead of 2
      
      2) increase tcp_rmem[2] limit from 4MB to 6MB to take into account
      better truesize tracking and to allow autotuning tcp receive window to
      reach same value than before. Note that same amount of kernel memory is
      consumed compared to 2.6 kernels.
      Signed-off-by: NEric Dumazet <edumazet@google.com>
      Cc: Neal Cardwell <ncardwell@google.com>
      Cc: Tom Herbert <therbert@google.com>
      Cc: Yuchung Cheng <ycheng@google.com>
      Acked-by: NNeal Cardwell <ncardwell@google.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b49960a0
    • Y
      tcp: early retransmit · eed530b6
      Yuchung Cheng 提交于
      This patch implements RFC 5827 early retransmit (ER) for TCP.
      It reduces DUPACK threshold (dupthresh) if outstanding packets are
      less than 4 to recover losses by fast recovery instead of timeout.
      
      While the algorithm is simple, small but frequent network reordering
      makes this feature dangerous: the connection repeatedly enter
      false recovery and degrade performance. Therefore we implement
      a mitigation suggested in the appendix of the RFC that delays
      entering fast recovery by a small interval, i.e., RTT/4. Currently
      ER is conservative and is disabled for the rest of the connection
      after the first reordering event. A large scale web server
      experiment on the performance impact of ER is summarized in
      section 6 of the paper "Proportional Rate Reduction for TCP”,
      IMC 2011. http://conferences.sigcomm.org/imc/2011/docs/p155.pdf
      
      Note that Linux has a similar feature called THIN_DUPACK. The
      differences are THIN_DUPACK do not mitigate reorderings and is only
      used after slow start. Currently ER is disabled if THIN_DUPACK is
      enabled. I would be happy to merge THIN_DUPACK feature with ER if
      people think it's a good idea.
      
      ER is enabled by sysctl_tcp_early_retrans:
        0: Disables ER
      
        1: Reduce dupthresh to packets_out - 1 when outstanding packets < 4.
      
        2: (Default) reduce dupthresh like mode 1. In addition, delay
           entering fast recovery by RTT/4.
      
      Note: mode 2 is implemented in the third part of this patch series.
      Signed-off-by: NYuchung Cheng <ycheng@google.com>
      Acked-by: NNeal Cardwell <ncardwell@google.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      eed530b6
  8. 27 4月, 2012 1 次提交
  9. 16 4月, 2012 1 次提交
  10. 11 4月, 2012 3 次提交
    • S
    • S
      batman-adv: add basic bridge loop avoidance code · 23721387
      Simon Wunderlich 提交于
      This second version of the bridge loop avoidance for batman-adv
      avoids loops between the mesh and a backbone (usually a LAN).
      
      By connecting multiple batman-adv mesh nodes to the same ethernet
      segment a loop can be created when the soft-interface is bridged
      into that ethernet segment. A simple visualization of the loop
      involving the most common case - a LAN as ethernet segment:
      
      node1  <-- LAN  -->  node2
        |                   |
      wifi   <-- mesh -->  wifi
      
      Packets from the LAN (e.g. ARP broadcasts) will circle forever from
      node1 or node2 over the mesh back into the LAN.
      
      With this patch, batman recognizes backbone gateways, nodes which are
      part of the mesh and backbone/LAN at the same time. Each backbone
      gateway "claims" clients from within the mesh to handle them
      exclusively. By restricting that only responsible backbone gateways
      may handle their claimed clients traffic, loops are effectively
      avoided.
      Signed-off-by: NSimon Wunderlich <siwu@hrz.tu-chemnitz.de>
      Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
      23721387
    • J
      mac80211: set HT channel before association · 24398e39
      Johannes Berg 提交于
      Changing the channel type during operation is
      confusing to some drivers and will be hard to
      handle in multi-channel scenarios. Instead of
      changing the channel, set it to the right HT
      channel before authenticating/associating and
      don't change it -- just update the 20/40 MHz
      restrictions in rate control as needed when
      changed by the AP.
      
      This also fixes a problem that Paul missed in
      his fix for the "regulatory makes us deaf"
      issue -- when we couldn't use 40 MHz we still
      associated saying we were using 40 MHz, which
      could in similarly broken APs make us never
      even connect successfully.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      24398e39
  11. 06 4月, 2012 5 次提交
  12. 05 4月, 2012 3 次提交
  13. 04 4月, 2012 1 次提交
  14. 31 3月, 2012 2 次提交
  15. 14 3月, 2012 1 次提交
  16. 13 3月, 2012 1 次提交
  17. 07 3月, 2012 1 次提交
  18. 05 3月, 2012 2 次提交
    • P
      ppp: Replace uses of <linux/if_ppp.h> with <linux/ppp-ioctl.h> · 4b32da2b
      Paul Mackerras 提交于
      Since all that include/linux/if_ppp.h does is #include <linux/ppp-ioctl.h>,
      this replaces the occurrences of #include <linux/if_ppp.h> with
      #include <linux/ppp-ioctl.h>.
      
      It also corrects an error in Documentation/networking/l2tp.txt, where
      it referenced include/linux/if_ppp.h as the source of some definitions
      that are actually now defined in include/linux/if_pppol2tp.h.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4b32da2b
    • P
      ppp: Move ioctl definitions from if_ppp.h to new ppp-ioctl.h · bf7daebb
      Paul Mackerras 提交于
      This moves the definitions of the ioctls, constants and structures
      relating to the ppp_generic interface to userspace out from if_ppp.h
      to a new file, ppp-ioctl.h.  The new file has my copyright since I
      designed and implemented the ppp_generic interface in the late 1990s.
      None of the contents of this file comes from the original if_ppp.h
      published by Carnegie Mellon University.
      
      Of the remainder of if_ppp.h, only the PPP_MTU definition was being
      used, and this replaces the uses of it with PPP_MRU (which is identical).
      Therefore, this replaces the entire file with the single line
      
      #include <linux/ppp-ioctl.h>
      
      which clearly doesn't contain any CMU code.  Thus I have removed the
      CMU copyright notice with its problematic advertising clause, and in
      fact since it's only one trivial line I have not added any other
      copyright notice.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      bf7daebb
  19. 24 2月, 2012 2 次提交
  20. 05 2月, 2012 1 次提交
  21. 31 1月, 2012 1 次提交
  22. 19 1月, 2012 1 次提交
  23. 27 12月, 2011 1 次提交
  24. 24 12月, 2011 1 次提交
  25. 22 12月, 2011 1 次提交
  26. 21 12月, 2011 1 次提交
  27. 07 12月, 2011 1 次提交
  28. 04 12月, 2011 1 次提交
    • J
      net: Add Open vSwitch kernel components. · ccb1352e
      Jesse Gross 提交于
      Open vSwitch is a multilayer Ethernet switch targeted at virtualized
      environments.  In addition to supporting a variety of features
      expected in a traditional hardware switch, it enables fine-grained
      programmatic extension and flow-based control of the network.
      This control is useful in a wide variety of applications but is
      particularly important in multi-server virtualization deployments,
      which are often characterized by highly dynamic endpoints and the need
      to maintain logical abstractions for multiple tenants.
      
      The Open vSwitch datapath provides an in-kernel fast path for packet
      forwarding.  It is complemented by a userspace daemon, ovs-vswitchd,
      which is able to accept configuration from a variety of sources and
      translate it into packet processing rules.
      
      See http://openvswitch.org for more information and userspace
      utilities.
      Signed-off-by: NJesse Gross <jesse@nicira.com>
      ccb1352e