From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [RFC] ethdev: add min/max MTU to device info Date: Thu, 6 Sep 2018 11:52:52 +0100 Message-ID: <20180906115252.79226596@shemminger-XPS-13-9360> References: <20180905164157.844-1-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: To: Andrew Rybchenko Return-path: Received: from mail-wr1-f68.google.com (mail-wr1-f68.google.com [209.85.221.68]) by dpdk.org (Postfix) with ESMTP id 38DDE325F for ; Thu, 6 Sep 2018 12:57:21 +0200 (CEST) Received: by mail-wr1-f68.google.com with SMTP id u12-v6so10873604wrr.4 for ; Thu, 06 Sep 2018 03:57:21 -0700 (PDT) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, 6 Sep 2018 09:29:32 +0300 Andrew Rybchenko wrote: > 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. Yes it is ABI change on 32 bit, but 18.11 is a major release where this is allowed/expected.