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>
Subject: Re: [dpdk-dev] [RFC] ethdev: add min/max MTU to device info
Date: Thu, 22 Nov 2018 09:58:30 +0000 [thread overview]
Message-ID: <CD7C01071941AC429549C17338DB8A52894E4693@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20180906115252.79226596@shemminger-XPS-13-9360>
> On Thu, 6 Sep 2018 09:29:32 +0300
> Andrew Rybchenko <arybchenko@solarflare.com> 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.
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 should be an ABI breakage notification in 18.11?
next prev parent reply other threads:[~2018-11-22 9:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 16:41 Stephen Hemminger
2018-09-06 5:51 ` Shahaf Shuler
2018-09-06 6:29 ` Andrew Rybchenko
2018-09-06 10:52 ` Stephen Hemminger
2018-11-22 9:58 ` Stokes, Ian [this message]
2018-12-19 2:37 ` Thomas Monjalon
2019-01-16 21:30 ` Stephen Hemminger
2019-02-06 13:05 ` Morten Brørup
2019-02-06 16:11 ` Stephen Hemminger
2019-02-06 21:58 ` Morten Brørup
2019-02-07 10:25 ` Ananyev, Konstantin
2019-02-07 11:10 ` Morten Brørup
2019-02-07 12:00 ` Ananyev, Konstantin
2019-02-20 16:02 ` Ian Stokes
2019-06-24 13:18 ` Nithin Kumar Dabilpuram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CD7C01071941AC429549C17338DB8A52894E4693@IRSMSX101.ger.corp.intel.com \
--to=ian.stokes@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).