All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Gasparakis <joseph.gasparakis@intel.com>
To: Or Gerlitz <ogerlitz@mellanox.com>
Cc: Joseph Gasparakis <joseph.gasparakis@intel.com>,
	Pravin B Shelar <pshelar@nicira.com>,
	Or Gerlitz <or.gerlitz@gmail.com>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	Jerry Chu <hkchu@google.com>, Eric Dumazet <edumazet@google.com>,
	Alexei Starovoitov <ast@plumgrid.com>,
	David Miller <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	jeffrey.t.kirsher@intel.com,
	John Fastabend <john.fastabend@gmail.com>
Subject: Re: vxlan/veth performance issues on net.git + latest kernels
Date: Fri, 6 Dec 2013 02:30:54 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.03.1312060205220.3499@intel.com> (raw)
In-Reply-To: <52A197DF.5010806@mellanox.com>



On Fri, 6 Dec 2013, Or Gerlitz wrote:

> On 04/12/2013 11:41, Or Gerlitz wrote:
> > On Wed, Dec 4, 2013 at 11:24 AM, Joseph
> > Gasparakis<joseph.gasparakis@intel.com>  wrote:
> > > >And just for the record,
> > > >you are seeing (SKB_UDP_TUNNEL | SKB_GSO_TCPV4) as 0x201 while I was
> > > >seeing it as 0x81 because commit 61c1db7fae "ipv6: sit: add GSO/TSO
> > > >support" pushed the SKB_UDP_TUNNEL two bits left, and I had done my tests
> > > before it.
> > indeed, also, on what kernel did you conducted your tests which you managed
> > to WA the problem with unsetting that bit?
> 
> 
> Hi Joseph,
> 
> Really need your response here --

I'm sorry Or, I managed to miss your original request...

> 
> 1. on which kernel did you manage to get along fine vxlan performance wise
> with this hack?
> 

I was running 3.10.6.

> 2. did the hack helped for both veth host traffic or only on PV VM traffic?
> 

No, just VM. I haven't tried veth.

If you leave the DODGY bit, does your traffic get droped on Tx, after it 
leaves vxlan and before it hits your driver, which is what I had seen. Is 
that right?

If you unset it, do you recover?

What is the output of your ethtool -k on the interface you are 
transmitting from?

> Currently it doesn't converge with 3.12.x or net.git, with veth/vxlan the
> DODGE bit isn't set when looking on the skb in the vxlan xmit time, so there's
> nothing for me to hack there. For VMs without unsetting the bit things don't
> really work, but unsetting it for itself so far didn't get me far performance
> wise.
> 
> BTW guys, I saw the issues with both bridge/openvswitch configuration - seems
> that we might have here somehow large breakage of the system w.r.t vxlan
> traffic for rates that go over few Gbs -- so would love to get feedback of any
> kind from the people that were involved with vxlan over the last months/year.
> 
> Or.
> 
> net.git]# grep -rn  SKB_GSO_DODGY drivers/net/ net/ipv4 net/core
> drivers/net/macvtap.c:585: skb_shinfo(skb)->gso_type |= SKB_GSO_DODGY;
> drivers/net/tun.c:1135:         skb_shinfo(skb)->gso_type |= SKB_GSO_DODGY;
> drivers/net/virtio_net.c:497: skb_shinfo(skb)->gso_type |= SKB_GSO_DODGY;
> drivers/net/xen-netback/netback.c:1146: skb_shinfo(skb)->gso_type |=
> SKB_GSO_DODGY;
> drivers/net/xen-netfront.c:823: skb_shinfo(skb)->gso_type |= SKB_GSO_DODGY;
> net/ipv4/af_inet.c:1264:                       SKB_GSO_DODGY |
> net/ipv4/tcp_offload.c:56: SKB_GSO_DODGY |
> net/ipv4/gre_offload.c:40: SKB_GSO_DODGY |
> net/ipv4/udp_offload.c:53:              if (unlikely(type & ~(SKB_GSO_UDP |
> SKB_GSO_DODGY |
> net/core/dev.c:2694:            if (shinfo->gso_type & SKB_GSO_DODGY)
> 
> 
> 

  parent reply	other threads:[~2013-12-06 10:13 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 15:05 vxlan/veth performance issues on net.git + latest kernels Or Gerlitz
2013-12-03 15:30 ` Eric Dumazet
2013-12-03 19:55   ` Or Gerlitz
2013-12-03 21:11     ` Joseph Gasparakis
2013-12-03 21:09       ` Or Gerlitz
2013-12-03 21:24         ` Eric Dumazet
2013-12-03 21:36           ` Or Gerlitz
2013-12-03 21:50             ` David Miller
2013-12-03 21:55               ` Eric Dumazet
2013-12-03 22:15                 ` Or Gerlitz
2013-12-03 22:22                 ` Or Gerlitz
2013-12-03 22:30                   ` Hannes Frederic Sowa
2013-12-03 22:35                     ` Or Gerlitz
2013-12-03 22:39                       ` Hannes Frederic Sowa
2013-12-03 23:10                 ` Or Gerlitz
2013-12-03 23:30                   ` Or Gerlitz
2013-12-03 23:49                     ` Hannes Frederic Sowa
2013-12-03 23:59                   ` Eric Dumazet
2013-12-04  0:26                     ` Alexei Starovoitov
2013-12-04  0:36                       ` Eric Dumazet
2013-12-04  0:55                         ` Alexei Starovoitov
2013-12-04  1:23                           ` Eric Dumazet
2013-12-04  1:59                             ` Alexei Starovoitov
2013-12-06  9:06                             ` Or Gerlitz
2013-12-06 13:36                               ` Eric Dumazet
2013-12-07 21:20                                 ` Or Gerlitz
2013-12-08 12:09                                 ` Or Gerlitz
2013-12-04  6:39                     ` David Miller
2013-12-04 17:40                       ` Eric Dumazet
2013-12-05 12:45                     ` [PATCH net-next] net: introduce dev_consume_skb_any() Eric Dumazet
2013-12-05 14:13                       ` Hannes Frederic Sowa
2013-12-05 14:45                         ` Eric Dumazet
2013-12-05 15:05                           ` Eric Dumazet
2013-12-05 15:44                             ` Hannes Frederic Sowa
2013-12-05 16:38                               ` Eric Dumazet
2013-12-05 16:54                                 ` Hannes Frederic Sowa
2013-12-06 20:24                       ` David Miller
2013-12-03 23:13         ` vxlan/veth performance issues on net.git + latest kernels Joseph Gasparakis
2013-12-03 23:09           ` Or Gerlitz
2013-12-04  0:35             ` Joseph Gasparakis
2013-12-04  0:34               ` Alexei Starovoitov
2013-12-04  1:29                 ` Joseph Gasparakis
2013-12-04  1:18                   ` Eric Dumazet
2013-12-04  0:44               ` Joseph Gasparakis
2013-12-04  8:35               ` Or Gerlitz
2013-12-04  9:24                 ` Joseph Gasparakis
2013-12-04  9:41                   ` Or Gerlitz
2013-12-04 15:20                     ` Or Gerlitz
     [not found]                     ` <52A197DF.5010806@mellanox.com>
2013-12-06  9:30                       ` Or Gerlitz
2013-12-08 12:43                         ` Mike Rapoport
2013-12-08 13:07                           ` Or Gerlitz
2013-12-08 14:30                             ` Mike Rapoport
2013-12-08 20:50                               ` Eric Dumazet
2013-12-08 21:36                                 ` Eric Dumazet
2013-12-06 10:30                       ` Joseph Gasparakis [this message]
2013-12-07 21:27                         ` Or Gerlitz
2013-12-08 18:08                           ` Joseph Gasparakis
2013-12-08 20:12                             ` Or Gerlitz
2013-12-08 15:21                         ` Or Gerlitz
2013-12-03 17:12 ` Eric Dumazet
2013-12-03 19:50   ` Or Gerlitz
2013-12-03 20:19     ` John Fastabend
2013-12-03 21:12     ` Eric Dumazet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.03.1312060205220.3499@intel.com \
    --to=joseph.gasparakis@intel.com \
    --cc=ast@plumgrid.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=hkchu@google.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=or.gerlitz@gmail.com \
    --cc=pshelar@nicira.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.