From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 944C01B5FA for ; Sat, 24 Nov 2018 18:37:35 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2D6772EAD0; Sat, 24 Nov 2018 12:37:35 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sat, 24 Nov 2018 12:37:35 -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=CoJegySHNJXT0tJ5xmAcVrvzuDdEuLyHj1i37isrsno=; b=hgSPoOpJlicq 2QFjPf5A23OOd+qUoQFVeP/Xpe0HyMAvmx5kr8Qhoe0ksrmbund5N3BZXnsbYkjK TcYY75jlg18GdAw09S8XQqEFNyLYTax4e+515+7z/JD5+ipXU7XGwqYn3j0Hq9MK 8YaPuSN9EZDHPHWNq9AoZVqL0S6Du04= 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=CoJegySHNJXT0tJ5xmAcVrvzuDdEuLyHj1i37isrs no=; b=YDKCk5/gDv7mlQ+hm2wwN/wTrHXVGPoJEggHSATh8E49YsoRAz62jRJqB aAtgzoMAUwxyQZyWDrCGUQO84snwkcU3A8u9XiyCzcw5FJjLljyv7Wfg+1He0CsR ZaPpcz3whNpxtZ5nSiT9yf9wZ2vS1ggFWI8a9geSDhod4ll+TkBTETNt/WorzrrC EwGTig4ChrGnfSr2pjbPBLQGX6gtIYrxA3Aa1hM5+F86GOawQjuFsvJy+5lJQDUC RatNJ0lni69JXQ1nAmxNlE+j0F0evmFPxud4Bw0L64YSgYef9tC++keLJfoygh8v lOovMH2nK78NtaMKHq6GZpvVlvubQ== X-ME-Sender: 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 D34A4E4898; Sat, 24 Nov 2018 12:37:33 -0500 (EST) From: Thomas Monjalon To: Ian Stokes Cc: dev@dpdk.org, Ferruh Yigit , stephen@networkplumber.org, arybchenko@solarflare.com Date: Sat, 24 Nov 2018 18:37:32 +0100 Message-ID: <4500215.eisG5GXybI@xps> In-Reply-To: <3746356.gW38syhklm@xps> References: <1542888549-24656-1-git-send-email-ian.stokes@intel.com> <0abfa3f0-0f58-3265-d156-4d8d9b670830@intel.com> <3746356.gW38syhklm@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1 1/1] doc: announce ethdev ABI change for rte_eth_dev_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: Sat, 24 Nov 2018 17:37:35 -0000 22/11/2018 18:15, Thomas Monjalon: > 22/11/2018 13:11, Ferruh Yigit: > > On 11/22/2018 12:09 PM, Ian Stokes wrote: > > > Maximum and minimum MTU values vary between hardware devices. In > > > hardware agnostic DPDK applications access to such information would > > > allow a more accurate way of validating and setting supported MTU values on > > > a per device basis rather than using a defined default for all devices. > > > > > > The following solution was proposed: > > > > > > http://mails.dpdk.org/archives/dev/2018-September/110959.html > > > > > > This patch adds a depreciation notice for ``rte_eth_dev_info`` as new > > > members will be added to represent min and max MTU values. These can be > > > added to fit a hole in the existing structure for amd64 but not for 32 bit, > > > as such ABI change will occur as size of the structure will be impacted. > > > > > > Signed-off-by: Ian Stokes > > > > Acked-by: Ferruh Yigit > Acked-by: Thomas Monjalon > Acked-by: Andrew Rybchenko Applied