1. 27 8月, 2016 1 次提交
    • X
      veth: sctp: add NETIF_F_SCTP_CRC to device features · c80fafbb
      Xin Long 提交于
      Commit b17c7069 ("loopback: sctp: add NETIF_F_SCTP_CSUM to device
      features") added NETIF_F_SCTP_CRC to device features for lo device to
      improve the performance of sctp over lo.
      
      This patch is to add NETIF_F_SCTP_CRC to device features for veth to
      improve the performance of sctp over veth.
      
      Before this patch:
        ip netns exec cs_client netperf -H 10.167.12.2 -t SCTP_STREAM -- -m 10K
        Recv   Send    Send
        Socket Socket  Message  Elapsed
        Size   Size    Size     Time     Throughput
        bytes  bytes   bytes    secs.    10^6bits/sec
      
        212992 212992  10240    10.00    1117.16
      
      After this patch:
        ip netns exec cs_client netperf -H 10.167.12.2 -t SCTP_STREAM -- -m 10K
        Recv   Send    Send
        Socket Socket  Message  Elapsed
        Size   Size    Size     Time     Throughput
        bytes  bytes   bytes    secs.    10^6bits/sec
      
        212992 212992  10240    10.20    1415.22
      Tested-by: NLi Shuang <tjlishuang@yeah.net>
      Signed-off-by: NXin Long <lucien.xin@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c80fafbb
  2. 22 4月, 2016 1 次提交
  3. 02 3月, 2016 1 次提交
    • P
      veth: implement ndo_set_rx_headroom · 163e5292
      Paolo Abeni 提交于
      The rx headroom for veth dev is the peer device needed_headroom.
      Avoid ping-pong updates setting the private flag IFF_PHONY_HEADROOM.
      
      This avoids skb head reallocation when forwarding from a veth dev
      towards a device adding some kind of encapsulation.
      
      When transmitting frames below the MTU size towards a vxlan device,
      this gives about 10% performance speed-up when OVS is used to connect
      the veth and the vxlan device and a little more when using a
      plain Linux bridge.
      Signed-off-by: NPaolo Abeni <pabeni@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      163e5292
  4. 23 12月, 2015 1 次提交
    • V
      veth: don’t modify ip_summed; doing so treats packets with bad checksums as good. · ce8c839b
      Vijay Pandurangan 提交于
      Packets that arrive from real hardware devices have ip_summed ==
      CHECKSUM_UNNECESSARY if the hardware verified the checksums, or
      CHECKSUM_NONE if the packet is bad or it was unable to verify it. The
      current version of veth will replace CHECKSUM_NONE with
      CHECKSUM_UNNECESSARY, which causes corrupt packets routed from hardware to
      a veth device to be delivered to the application. This caused applications
      at Twitter to receive corrupt data when network hardware was corrupting
      packets.
      
      We believe this was added as an optimization to skip computing and
      verifying checksums for communication between containers. However, locally
      generated packets have ip_summed == CHECKSUM_PARTIAL, so the code as
      written does nothing for them. As far as we can tell, after removing this
      code, these packets are transmitted from one stack to another unmodified
      (tcpdump shows invalid checksums on both sides, as expected), and they are
      delivered correctly to applications. We didn’t test every possible network
      configuration, but we tried a few common ones such as bridging containers,
      using NAT between the host and a container, and routing from hardware
      devices to containers. We have effectively deployed this in production at
      Twitter (by disabling RX checksum offloading on veth devices).
      
      This code dates back to the first version of the driver, commit
      <e314dbdc> ("[NET]: Virtual ethernet device driver"), so I
      suspect this bug occurred mostly because the driver API has evolved
      significantly since then. Commit <0b796750> ("net/veth: Fix
      packet checksumming") (in December 2010) fixed this for packets that get
      created locally and sent to hardware devices, by not changing
      CHECKSUM_PARTIAL. However, the same issue still occurs for packets coming
      in from hardware devices.
      Co-authored-by: NEvan Jones <ej@evanjones.ca>
      Signed-off-by: NEvan Jones <ej@evanjones.ca>
      Cc: Nicolas Dichtel <nicolas.dichtel@6wind.com>
      Cc: Phil Sutter <phil@nwl.cc>
      Cc: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
      Cc: netdev@vger.kernel.org
      Cc: linux-kernel@vger.kernel.org
      Signed-off-by: NVijay Pandurangan <vijayp@vijayp.ca>
      Acked-by: NCong Wang <cwang@twopensource.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ce8c839b
  5. 19 8月, 2015 1 次提交
  6. 04 8月, 2015 1 次提交
  7. 03 4月, 2015 1 次提交
  8. 24 1月, 2015 1 次提交
  9. 16 7月, 2014 1 次提交
  10. 26 6月, 2014 1 次提交
  11. 29 3月, 2014 1 次提交
  12. 15 3月, 2014 1 次提交
  13. 20 2月, 2014 1 次提交
  14. 19 2月, 2014 1 次提交
  15. 15 2月, 2014 1 次提交
  16. 06 11月, 2013 1 次提交
    • J
      net: Explicitly initialize u64_stats_sync structures for lockdep · 827da44c
      John Stultz 提交于
      In order to enable lockdep on seqcount/seqlock structures, we
      must explicitly initialize any locks.
      
      The u64_stats_sync structure, uses a seqcount, and thus we need
      to introduce a u64_stats_init() function and use it to initialize
      the structure.
      
      This unfortunately adds a lot of fairly trivial initialization code
      to a number of drivers. But the benefit of ensuring correctness makes
      this worth while.
      
      Because these changes are required for lockdep to be enabled, and the
      changes are quite trivial, I've not yet split this patch out into 30-some
      separate patches, as I figured it would be better to get the various
      maintainers thoughts on how to best merge this change along with
      the seqcount lockdep enablement.
      
      Feedback would be appreciated!
      Signed-off-by: NJohn Stultz <john.stultz@linaro.org>
      Acked-by: NJulian Anastasov <ja@ssi.bg>
      Signed-off-by: NPeter Zijlstra <peterz@infradead.org>
      Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Eric Dumazet <eric.dumazet@gmail.com>
      Cc: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
      Cc: James Morris <jmorris@namei.org>
      Cc: Jesse Gross <jesse@nicira.com>
      Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
      Cc: "Michael S. Tsirkin" <mst@redhat.com>
      Cc: Mirko Lindner <mlindner@marvell.com>
      Cc: Patrick McHardy <kaber@trash.net>
      Cc: Roger Luethi <rl@hellgate.ch>
      Cc: Rusty Russell <rusty@rustcorp.com.au>
      Cc: Simon Horman <horms@verge.net.au>
      Cc: Stephen Hemminger <stephen@networkplumber.org>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
      Cc: Wensong Zhang <wensong@linux-vs.org>
      Cc: netdev@vger.kernel.org
      Link: http://lkml.kernel.org/r/1381186321-4906-2-git-send-email-john.stultz@linaro.orgSigned-off-by: NIngo Molnar <mingo@kernel.org>
      827da44c
  17. 28 10月, 2013 1 次提交
  18. 10 10月, 2013 1 次提交
  19. 09 10月, 2013 2 次提交
  20. 20 7月, 2013 1 次提交
    • F
      veth: add vlan features · b69bbddf
      Flavio Leitner 提交于
      The veth device doesn't provide the vlan features,
      so TSO for example is disabled and that causes
      performance issues when using tagged traffic.
      
      The test topology looks like this:
      
          br0                     br1
        /   \                  /     \
      vnet  veth0.10 ----- veth1.10   vnet
      VM                               VM
      
      The netperf results with current veth driver:
      MIGRATED TCP STREAM TEST from 192.168.1.1 ()
      port 0 AF_INET to 192.168.1.2 () port 0 AF_INET
      Recv   Send    Send
      Socket Socket  Message  Elapsed
      Size   Size    Size     Time     Throughput
      bytes  bytes   bytes    secs.    10^6bits/sec
      
       87380  16384  16384    10.01    2210.22
      
      Now after applying the proposed patch:
      MIGRATED TCP STREAM TEST from 192.168.1.1 ()
      port 0 AF_INET to 192.168.1.2 () port 0 AF_INET
      Recv   Send    Send
      Socket Socket  Message  Elapsed
      Size   Size    Size     Time     Throughput
      bytes  bytes   bytes    secs.    10^6bits/sec
      
       87380  16384  16384    10.00    13067.47
      Signed-off-by: NFlavio Leitner <fbl@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b69bbddf
  21. 12 6月, 2013 1 次提交
  22. 20 4月, 2013 2 次提交
  23. 11 2月, 2013 1 次提交
  24. 11 1月, 2013 1 次提交
  25. 08 1月, 2013 1 次提交
    • E
      veth: avoid a NULL deref in veth_stats_one · d0e2c55e
      Eric Dumazet 提交于
      commit 2681128f (veth: extend device features) added a NULL deref
      in veth_stats_one(), as veth_get_stats64() was not testing if the peer
      device was setup or not.
      
      At init time, we call dev_get_stats() before veth pair is fully setup.
      
      [  178.854758]  [<ffffffffa00f5677>] veth_get_stats64+0x47/0x70 [veth]
      [  178.861013]  [<ffffffff814f0a2d>] dev_get_stats+0x6d/0x130
      [  178.866486]  [<ffffffff81504efc>] rtnl_fill_ifinfo+0x47c/0x930
      [  178.872299]  [<ffffffff81505b93>] rtmsg_ifinfo+0x83/0x100
      [  178.877678]  [<ffffffff81505cc6>] rtnl_configure_link+0x76/0xa0
      [  178.883580]  [<ffffffffa00f52fa>] veth_newlink+0x16a/0x350 [veth]
      [  178.889654]  [<ffffffff815061cc>] rtnl_newlink+0x4dc/0x5e0
      [  178.895128]  [<ffffffff81505e1e>] ? rtnl_newlink+0x12e/0x5e0
      [  178.900769]  [<ffffffff8150587d>] rtnetlink_rcv_msg+0x11d/0x310
      [  178.906669]  [<ffffffff81505760>] ? __rtnl_unlock+0x20/0x20
      [  178.912225]  [<ffffffff81521f89>] netlink_rcv_skb+0xa9/0xd0
      [  178.917779]  [<ffffffff81502d55>] rtnetlink_rcv+0x25/0x40
      [  178.923159]  [<ffffffff815218d1>] netlink_unicast+0x1b1/0x230
      [  178.928887]  [<ffffffff81521c4e>] netlink_sendmsg+0x2fe/0x3b0
      [  178.934615]  [<ffffffff814dbe22>] sock_sendmsg+0xd2/0xf0
      
      So we must check if peer was setup in veth_get_stats64()
      
      As pointed out by Ben Hutchings, priv->peer is missing proper
      synchronization. Adding RCU protection is a safe and well documented
      way to make sure we don't access about to be freed or already
      freed data.
      Reported-by: NTom Parkin <tparkin@katalix.com>
      Signed-off-by: NEric Dumazet <edumazet@google.com>
      CC: Ben Hutchings <bhutchings@solarflare.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d0e2c55e
  26. 30 12月, 2012 2 次提交
  27. 01 12月, 2012 1 次提交
    • R
      rtnelink: remove unused parameter from rtnl_create_link(). · c0713563
      Rami Rosen 提交于
      This patch removes an unused parameter (src_net) from rtnl_create_link()
      method and from the method single invocation, in veth.
      This parameter was used in the past when calling
      ops->get_tx_queues(src_net, tb) in rtnl_create_link().
      The get_tx_queues() member of rtnl_link_ops was replaced by two methods,
      get_num_tx_queues() and get_num_rx_queues(), which do not get any
      parameter. This was done in commit d40156aa by
      Jiri Pirko ("rtnl: allow to specify different num for rx and tx queue count").
      Signed-off-by: NRami Rosen <ramirose@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c0713563
  28. 02 11月, 2012 1 次提交
  29. 10 8月, 2012 1 次提交
    • P
      veth: Allow to create peer link with given ifindex · e6f8f1a7
      Pavel Emelyanov 提交于
      The ifinfomsg is in there (thanks kaber@ for foreseeing this long time ago),
      so take the given ifidex and register netdev with it.
      
      Ben noticed, that this code path previously ignored ifmp->ifi_index and
      userland could be passing in garbage. Thus it may now fail occasionally
      because the value clashes with an existing interface.
      
      To address this it's assumed that if the caller specifies the ifindex for
      the veth master device, then it's aware of this possibility and should
      explicitly specify (or set to 0 for auto-assignment) the peer's ifindex as
      well. With this the compatibility with old tools not setting ifindex is
      preserved.
      Signed-off-by: NPavel Emelyanov <xemul@parallels.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e6f8f1a7
  30. 16 2月, 2012 2 次提交
  31. 23 11月, 2011 1 次提交
  32. 17 11月, 2011 2 次提交
  33. 09 11月, 2011 1 次提交
  34. 01 11月, 2011 1 次提交
  35. 28 7月, 2011 1 次提交
    • N
      net: Audit drivers to identify those needing IFF_TX_SKB_SHARING cleared · 550fd08c
      Neil Horman 提交于
      After the last patch, We are left in a state in which only drivers calling
      ether_setup have IFF_TX_SKB_SHARING set (we assume that drivers touching real
      hardware call ether_setup for their net_devices and don't hold any state in
      their skbs.  There are a handful of drivers that violate this assumption of
      course, and need to be fixed up.  This patch identifies those drivers, and marks
      them as not being able to support the safe transmission of skbs by clearning the
      IFF_TX_SKB_SHARING flag in priv_flags
      Signed-off-by: NNeil Horman <nhorman@tuxdriver.com>
      CC: Karsten Keil <isdn@linux-pingi.de>
      CC: "David S. Miller" <davem@davemloft.net>
      CC: Jay Vosburgh <fubar@us.ibm.com>
      CC: Andy Gospodarek <andy@greyhouse.net>
      CC: Patrick McHardy <kaber@trash.net>
      CC: Krzysztof Halasa <khc@pm.waw.pl>
      CC: "John W. Linville" <linville@tuxdriver.com>
      CC: Greg Kroah-Hartman <gregkh@suse.de>
      CC: Marcel Holtmann <marcel@holtmann.org>
      CC: Johannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      550fd08c