From mboxrd@z Thu Jan 1 00:00:00 1970 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) 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=VET8xgATI1v6b7MR/Ox11f3777NVsfV3HWcg3Ru+h48=; b=pMABtiW5jA3S+f+kJhdRdj5a+w8YyZoeqMGdKq4prznnuTQWWY6Th4U15vmI5+Dsgr 5jQCLba7bz+Lqb0ieSR9YTg1ajoCvqvnkG5o+MoIbrDJW/im6YA6UFoXGG37FVtzC++r yhOOuJY8MPu06HvUi7IRzARGcgRQUmAsNb9G+paQ2ujijv/VyHSUabRrWydldmX8/ZgK mh/ZdujKWeXaWGuhIpoWlbwL7XboajERZRc6VFEEVNgVnHGYTE6ibpdKfPfDfqhpb4Cj LBT/9luUeoK/JrvF+4yri1X9SjSi94PGiPj3Od899n9uwky5dmlU1slEWlEqTVlOBWv9 3VTg== 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=VET8xgATI1v6b7MR/Ox11f3777NVsfV3HWcg3Ru+h48=; b=YfTAS533wbwtbYUKlujq8jzG69ZU6hRa71Qt5tsKqDGykkFcCzga9QlsS9wr5OaUPy NwdUcOpf6jlDupw/iE1Nfa0AeFLqSJ/jeXTtw/U50eNr6dyUK9oV/0hbTk7upYsOJdLw buKD21Iii4T+M+7oLmjUKjIy7PXOpNhLMUaKKf/eQUHYlyhlMXNAJeAPJlrjIASceDmh t2GOlPXhMEcE80BXJdo5+/9xQX/mw9xRc6RoC+ntELqb5gFAbwjfOSsoPupJZKVS08di v5FB/W3uXzlYkGhyfAojuR1iG1Pdn571Ybl0juk4Ssg00lI1Uzo89TZzWk1YCybU5MCl n2uQ== X-Gm-Message-State: APzg51AyzeVUmxbSyZPR0DZaYH8EVAibR9o7vFw1J8m58vB2L/zPVcXG c8NaluW3LDGC5pH6YUSy5dW9FA== X-Google-Smtp-Source: ANB0VdYuxb8UaJSpIV2ZMfBzw0gYTEVlCLRsg+373NicXYojkWsMGf9MY4N/UjY98CHQR3IiCW9VdQ== X-Received: by 2002:a5d:45cb:: with SMTP id b11-v6mr1856830wrs.122.1536231440695; Thu, 06 Sep 2018 03:57:20 -0700 (PDT) Received: from shemminger-XPS-13-9360 ([31.216.236.195]) by smtp.gmail.com with ESMTPSA id x24-v6sm7064741wrd.13.2018.09.06.03.57.20 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 06 Sep 2018 03:57:20 -0700 (PDT) Date: Thu, 6 Sep 2018 11:52:52 +0100 From: Stephen Hemminger To: Andrew Rybchenko Cc: Message-ID: <20180906115252.79226596@shemminger-XPS-13-9360> In-Reply-To: References: <20180905164157.844-1-stephen@networkplumber.org> 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: Thu, 06 Sep 2018 10:57:21 -0000 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.