From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 0ECB617D5; Tue, 18 Dec 2018 21:37:18 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 18 Dec 2018 21:37:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=/idDJFcwtS2qNGL21IYFQACz1/7l4I/HrhUNGnhC9jg=; b=s/BUjaZ8AryQ zG9/c03Ob/yyHMRJXvXgZTHFNfCNgFwrlRRfftfb9qMljCxS34V5hk7xsFSy+tA8 OD9PxIFQBnFG47f35ZxgZeTgqoFcj50exYL3a3Y6dH5hTl5F4Fhdmfq+s3q1PnLG SgT8HSt8blkVKmQl8/rdhBgTrA0R/bM= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=/idDJFcwtS2qNGL21IYFQACz1/7l4I/HrhUNGnhC9 jg=; b=axlrhoohmLS8TY0+DvKq7ee+BEkz3i0+cAtTd3os7GCoL30EY5YrC5lOb TbJ/QOSkcnoj7K4cnZYx9c9f4FGYH/tkONSU1nn3tRLwbcBrVYeKqy1S12Cfn5pb qdig6idyK4jCSxjrojDd0CvE+6ZXPsalkkEyKDJKVQR41SRiKE05i446ryP0D2jJ SLGlEDVW8ct0/ClzOPZZjtdZu4iwV4SSzHz2UcffzRdYHHL3ui6kABKPKSpGkbQZ dkLEvo6mM4IIejpYpkcMPWYw6Zf775cNXy6C62rzDl5SqaxbDHqLsUsoW9Yu6pJI w0q4oqCOfiSzU5moZmEDmpibSTRmQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudeiledgudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvffufffkjg hfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcu oehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkphepjeejrddufeegrddvtd efrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 6EE3A100B9; Tue, 18 Dec 2018 21:37:17 -0500 (EST) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org, ferruh.yigit@intel.com, arybchenko@solarflare.com Date: Wed, 19 Dec 2018 03:37:16 +0100 Message-ID: <2810348.XpGyddNB5W@xps> In-Reply-To: <20180905164157.844-1-stephen@networkplumber.org> References: <20180905164157.844-1-stephen@networkplumber.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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, 19 Dec 2018 02:37:20 -0000 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