Re: [ovs-dev] [RFC PATCH v2 1/1] netdev-dpdk: enable multi-segment jumbo frames

2017-05-31 Thread Kavanagh, Mark B
>From: Chandran, Sugesh >Sent: Friday, May 26, 2017 8:07 PM >To: Kavanagh, Mark B <mark.b.kavan...@intel.com>; ovs-dev@openvswitch.org; >qiud...@chinac.com >Subject: RE: [ovs-dev] [RFC PATCH v2 1/1] netdev-dpdk: enable multi-segment >jumbo frames > > >

Re: [ovs-dev] [RFC PATCH v2 1/1] netdev-dpdk: enable multi-segment jumbo frames

2017-05-26 Thread Chandran, Sugesh
Regards _Sugesh > -Original Message- > From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev- > boun...@openvswitch.org] On Behalf Of Mark Kavanagh > Sent: Monday, May 15, 2017 11:17 AM > To: ovs-dev@openvswitch.org; qiud...@chinac.com > Subject: [ovs-dev] [RFC PA

Re: [ovs-dev] [RFC PATCH v2 1/1] netdev-dpdk: enable multi-segment jumbo frames

2017-05-16 Thread 仇大玉
2017/5/15 18:17, Mark Kavanagh : Currently, jumbo frame support for OvS-DPDK is implemented by increasing the size of mbufs within a mempool, such that each mbuf within the pool is large enough to contain an entire jumbo frame of a user-defined size. Typically, for each user-defined MTU

[ovs-dev] [RFC PATCH v2 1/1] netdev-dpdk: enable multi-segment jumbo frames

2017-05-15 Thread Mark Kavanagh
Currently, jumbo frame support for OvS-DPDK is implemented by increasing the size of mbufs within a mempool, such that each mbuf within the pool is large enough to contain an entire jumbo frame of a user-defined size. Typically, for each user-defined MTU 'requested_mtu', a new mempool is created,