From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f193.google.com (mail-pf1-f193.google.com [209.85.210.193]) by dpdk.org (Postfix) with ESMTP id 433DF1041 for ; Wed, 16 Jan 2019 22:30:53 +0100 (CET) Received: by mail-pf1-f193.google.com with SMTP id z9so3692873pfi.2 for ; Wed, 16 Jan 2019 13:30:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=nHd5RF4eL6mYUTkxBWX0o/pzRGNuTz8yOrYaXnPUT3w=; b=BXNVqd8Apl3OAlRicUAtCHiKhzAzXrN0PARftfRVdjHeK3ahfI1agV6kkjIEgDNSfl zz8qZSO4raDRlNz2694EeycMFFr5DD7m3AfNWJnOC5sqo2tMsoN+rubgg3C3QR6Dgu1C AGyNpfsSibE3rCkJcozmrmZB5VucGTQ2rPDtQfUswPbf5yK+BTD4uRUJ+FuoDinwjbsq aoEvKYnUnUUmnV733YxaNFUPAaJ5vU3+db72P1zORy514QlSh1nbgTEKnDz8TZKKcQcR /KDdnJk0JT8uriGlJKpAuImg22H+9wZoVLFzBgL1phk9AUnF/UDvbZyTgpNPCnvtYCut ulsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=nHd5RF4eL6mYUTkxBWX0o/pzRGNuTz8yOrYaXnPUT3w=; b=eIkcjevtmpcBhyfDvjFUFtN8xxs+4264vzCq5tjNA/glgEMCLDrtc1djN6tULgH+F0 XVcvFMAR4uvhXkoqY5gSX6zpvoa3At3ORTxhFIZCDX7sXPmBeP5J+XfYiorkU+od9bNF if4Xnrh6pkZTwpexTFWydpFZ7mzXYXS+O1JiGIJBZSHNQ0xY/Zh/ikB34gztGmNfCN6u nbtBzU18Jcf+nPI0U2W3TEaHa2AGiTpCm23BjuKyUoDTTp45p4IEB8RE9IW/6LS1Xfpg 0iGAruHwWYFf0mdDDKr4k4dtacZ0Otgpe6XBbC8QPHC3sIuIwEoLaBNLZAVGsDpEOgn4 OVQQ== X-Gm-Message-State: AJcUukfXsvdhikK+bgSnoIMpiTIbsDyIHioFbpbVaDplaJmHabZvJMsJ D2+41nM8uLV9FKRoAIscQk1Jcg== X-Google-Smtp-Source: ALg8bN7SWcnd0XmRc6R51LrZ+xCZws4Y3bzqJOfVfhRTrjZbkTF/dcVa0KaS6mvq0BbNMO99uGWs9Q== X-Received: by 2002:a65:47ca:: with SMTP id f10mr11024202pgs.166.1547674251319; Wed, 16 Jan 2019 13:30:51 -0800 (PST) Received: from shemminger-XPS-13-9360 ([167.220.100.105]) by smtp.gmail.com with ESMTPSA id h74sm11453927pfd.35.2019.01.16.13.30.50 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 16 Jan 2019 13:30:50 -0800 (PST) Date: Wed, 16 Jan 2019 13:30:49 -0800 From: Stephen Hemminger To: Thomas Monjalon Cc: dev@dpdk.org, ferruh.yigit@intel.com, arybchenko@solarflare.com Message-ID: <20190116133049.029292da@shemminger-XPS-13-9360> In-Reply-To: <2810348.XpGyddNB5W@xps> References: <20180905164157.844-1-stephen@networkplumber.org> <2810348.XpGyddNB5W@xps> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [RFC] ethdev: add min/max MTU to device info X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jan 2019 21:30:53 -0000 On Wed, 19 Dec 2018 03:37:16 +0100 Thomas Monjalon wrote: > 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 > > > > It needs more than just this patch to be worthwhile. Need device drivers to fill in the max_mtu field, otherwise it would just break jumbo frame support. I suppose an initial patch to bump ethdev version would be possible for 19.05, are there other API changes doing that already for that relaease.