From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ian.stokes@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id 1A0AA1B217
 for <dev@dpdk.org>; Thu, 22 Nov 2018 10:58:33 +0100 (CET)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga003.jf.intel.com ([10.7.209.27])
 by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
 22 Nov 2018 01:58:32 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.56,265,1539673200"; d="scan'208";a="102271129"
Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75])
 by orsmga003.jf.intel.com with ESMTP; 22 Nov 2018 01:58:31 -0800
Received: from irsmsx101.ger.corp.intel.com ([169.254.1.134]) by
 IRSMSX153.ger.corp.intel.com ([169.254.9.139]) with mapi id 14.03.0415.000;
 Thu, 22 Nov 2018 09:58:30 +0000
From: "Stokes, Ian" <ian.stokes@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, Andrew Rybchenko
 <arybchenko@solarflare.com>
CC: "dev@dpdk.org" <dev@dpdk.org>, Shahaf Shuler <shahafs@mellanox.com>
Thread-Topic: [dpdk-dev] [RFC] ethdev: add min/max MTU to device info
Thread-Index: AQHURTd7Ns5c9hPsvUSFJ5ziTajwnaTiur4AgABJkwCAeQRp0A==
Date: Thu, 22 Nov 2018 09:58:30 +0000
Message-ID: <CD7C01071941AC429549C17338DB8A52894E4693@IRSMSX101.ger.corp.intel.com>
References: <20180905164157.844-1-stephen@networkplumber.org>
 <b817acca-439d-da4f-311d-13b5a25cb417@solarflare.com>
 <20180906115252.79226596@shemminger-XPS-13-9360>
In-Reply-To: <20180906115252.79226596@shemminger-XPS-13-9360>
Accept-Language: en-IE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMDk3MTQ4NGMtZTZkMC00ZDdiLTk0MzQtMDNhOGFjZjU3MTVmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoibDBDOTdRc2ZqaUl5eVRTWDVVTzNnNkxlQXIxaFQ5RjBaUHl4bkZZdjN3ZVhZNVAwd2JmbXlXaFdBRUJ3dlhSOSJ9
x-ctpclassification: CTP_NT
dlp-product: dlpe-windows
dlp-version: 11.0.400.15
dlp-reaction: no-action
x-originating-ip: [163.33.239.180]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Nov 2018 09:58:34 -0000

> On Thu, 6 Sep 2018 09:29:32 +0300
> Andrew Rybchenko <arybchenko@solarflare.com> wrote:
>=20
> > On 09/05/2018 07:41 PM, Stephen Hemminger wrote:
> > > 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.
> >
> > It is true for amd64, but it looks like it is false on 32-bit. So, ABI
> > breakage.
>=20
> Yes it is ABI change on 32 bit, but 18.11 is a major release where this i=
s
> allowed/expected.

Thanks for this work Stephen, I've tested it with OVS DPDK and it resolves =
the issues as described, if it's to be part of DPDK 19.02 I guess there sho=
uld be an ABI breakage notification in 18.11?