From: Or Gerlitz <or.gerlitz@gmail.com>
To: Wei-Chun Chao <weichunc@plumgrid.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
Alexei Starovoitov <ast@plumgrid.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Joseph Gasparakis <joseph.gasparakis@intel.com>
Subject: Re: [PATCH net-next] ipv4: fix tunneled VM traffic over hw VXLAN/GRE GSO NIC
Date: Sun, 22 Dec 2013 15:25:53 +0200 [thread overview]
Message-ID: <CAJZOPZJsm08_EnGsitbx_qoHk28+TEnORJB__b9Zi284kcfkJw@mail.gmail.com> (raw)
In-Reply-To: <1387393368-1028-1-git-send-email-weichunc@plumgrid.com>
On Wed, Dec 18, 2013 at 9:02 PM, Wei-Chun Chao <weichunc@plumgrid.com> wrote:
> This is also seen on 'net'.
>
> VM to VM GSO traffic is broken if it goes through VXLAN or GRE
> tunnel and the physical NIC on the host supports hardware VXLAN/GRE
> GSO offload (e.g. bnx2x and next-gen mlx4).
Ack, this patch solves the breakage of VM traffic that is subject to
offloaded vxlan traffic which I see with latest kernels and the mlx4
patches I posted last week. So how we make progress here, is this
patch getting in or the alternative suggested down the thread by
Wei-Chun here http://patchwork.ozlabs.org/patch/303025/?
next prev parent reply other threads:[~2013-12-22 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 19:02 [PATCH net-next] ipv4: fix tunneled VM traffic over hw VXLAN/GRE GSO NIC Wei-Chun Chao
2013-12-19 0:35 ` Stephen Hemminger
2013-12-19 1:51 ` Wei-Chun Chao
2013-12-19 2:05 ` Stephen Hemminger
2013-12-19 6:20 ` Or Gerlitz
2013-12-22 13:25 ` Or Gerlitz [this message]
2013-12-26 18:10 ` David Miller
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=CAJZOPZJsm08_EnGsitbx_qoHk28+TEnORJB__b9Zi284kcfkJw@mail.gmail.com \
--to=or.gerlitz@gmail.com \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=joseph.gasparakis@intel.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=weichunc@plumgrid.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).