netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Zhangming (James, Euler)" <james.zhangming@huawei.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Vlad Yasevic <vyasevic@redhat.com>
Subject: Re: Virtio_net support vxlan encapsulation package TSO offload discuss
Date: Tue, 8 Nov 2016 19:17:25 +0800	[thread overview]
Message-ID: <3a0b8f10-f479-3ed5-dd10-5b92de3eb593@redhat.com> (raw)
In-Reply-To: <c2f735e4-eddf-f737-2afe-35a93289f8d4@redhat.com>



On 2016年11月08日 19:13, Jason Wang wrote:
> Cc Michael
>
> On 2016年11月08日 16:34, Zhangming (James, Euler) wrote:
>>
>> In container scenario, OVS is installed in the Virtual machine, and 
>> all the containers connected to the OVS will communicated through 
>> VXLAN encapsulation.
>>
>> By now, virtio_net does not support TSO offload for VXLAN 
>> encapsulated TSO package. In this condition, the performance is not 
>> good, sender is bottleneck
>>
>> I googled this scenario, but I didn’t find any information. Will 
>> virtio_net support VXLAN encapsulation package TSO offload later?
>>
>
> Yes and for both sender and receiver.
>
>> My idea is virtio_net open encapsulated TSO offload, and transport 
>> encapsulation info to TUN, TUN will parse the info and build skb with 
>> encapsulation info.
>>
>> OVS or kernel on the host should be modified to support this. Using 
>> this method, the TCP performance aremore than 2x as before.
>>
>> Any advice and suggestions for this idea or new idea will be greatly 
>> appreciated!
>>
>> Best regards,
>>
>>    James zhang
>>
>
> Sounds very good. And we may also need features bits 
> (VIRTIO_NET_F_GUEST|HOST_GSO_X) for this.
>
> This is in fact one of items in networking todo list. (See 
> http://www.linux-kvm.org/page/NetworkingTodo). While at it, we'd 
> better support not only VXLAN but also other tunnels.

Cc Vlad who is working on extending virtio-net headers.

>
> We can start with the spec work, or if you've already had some bits 
> you can post them as RFC for early review.
>
> Thanks

  reply	other threads:[~2016-11-08 11:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DBCD2614ECF3FF4087A2C27CA80E34DD5401AC8B@SZXEMA501-MBX.china.huawei.com>
2016-11-08 11:13 ` Virtio_net support vxlan encapsulation package TSO offload discuss Jason Wang
2016-11-08 11:17   ` Jason Wang [this message]
2016-11-08 11:58     ` Zhangming (James, Euler)
2016-11-09  7:14       ` Jason Wang
2016-11-10  6:19         ` Zhangming (James, Euler)
2016-11-15  3:27           ` Jason Wang
2016-11-17  1:31             ` Zhangming (James, Euler)
2016-11-17  7:27               ` Jason Wang
2016-11-17 23:10                 ` Jarno Rajahalme

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=3a0b8f10-f479-3ed5-dd10-5b92de3eb593@redhat.com \
    --to=jasowang@redhat.com \
    --cc=james.zhangming@huawei.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=vyasevic@redhat.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).