[ovs-discuss] OVS-DPDK IP fragmentation require

Darrell Ball dball at vmware.com
Thu Jul 27 06:49:42 UTC 2017

From: Hui Xiang <xianghuir at gmail.com>
Date: Wednesday, July 26, 2017 at 9:43 PM
To: Darrell Ball <dball at vmware.com>
Cc: "ovs-discuss at openvswitch.org" <ovs-discuss at openvswitch.org>
Subject: Re: [ovs-discuss] OVS-DPDK IP fragmentation require

Thanks Darrell, comment inline.

On Thu, Jul 27, 2017 at 12:08 PM, Darrell Ball <dball at vmware.com<mailto:dball at vmware.com>> wrote:

From: <ovs-discuss-bounces at openvswitch.org<mailto:ovs-discuss-bounces at openvswitch.org>> on behalf of Hui Xiang <xianghuir at gmail.com<mailto:xianghuir at gmail.com>>
Date: Wednesday, July 26, 2017 at 7:47 PM
To: "ovs-discuss at openvswitch.org<mailto:ovs-discuss at openvswitch.org>" <ovs-discuss at openvswitch.org<mailto:ovs-discuss at openvswitch.org>>
Subject: [ovs-discuss] OVS-DPDK IP fragmentation require

Hi guys,

  Seems OVS-DPDK still missing IP fragmentation support, is there any schedule to have it?
OVS 2.9
I'm  transferring to use OVN, but for those nodes which have external network connection, they may face this problem,
except to configure Jumbo frames, is there any other workaround?

I am not clear on the situation however.
You mention about configuring jumbo frames which means you can avoid the fragments by doing this ?
No, I can't guarantee that, only can do it inside OpenStack, it is limited.
If this is true, then this is the best way to proceed since performance will be better.
What is wrong with jumbo frames ?
It's good but it's limited can't be guaranteed, so I am asking is there any other way without IP fragmentation so far.

It sounds like you want to avoid IP fragmentation; so far so good.
I am not sure I understand the whole picture though.
Maybe you can describe what you see ?; maybe a simple diagram would help ?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20170727/7351e2e3/attachment.html>

More information about the discuss mailing list