From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [RFC] ethdev: add min/max MTU to device info Date: Wed, 19 Dec 2018 03:37:16 +0100 Message-ID: <2810348.XpGyddNB5W@xps> References: <20180905164157.844-1-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, ferruh.yigit@intel.com, arybchenko@solarflare.com To: Stephen Hemminger Return-path: Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 4E22A1B5E8 for ; Wed, 19 Dec 2018 03:37:20 +0100 (CET) In-Reply-To: <20180905164157.844-1-stephen@networkplumber.org> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Stephen, Can we expect a v2 of this patch? At least for removing deprecation and bump ethdev version, etc? 05/09/2018 18:41, Stephen Hemminger: > This addresses the usability issue raised by OVS at DPDK Userspace > summit. It adds general min/max mtu into device info. For compatiablity, > and to save space, it fits in a hole in existing structure. > > The initial version sets max mtu to normal Ethernet, it is up to > PMD to set larger value if it supports Jumbo frames. > > Fixing the drivers to use this is trivial and can be done by 18.11. > Already have some of the patches done. > > Signed-off-by: Stephen Hemminger