From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, arybchenko@solarflare.com
Subject: Re: [dpdk-dev] [RFC] ethdev: add min/max MTU to device info
Date: Wed, 16 Jan 2019 13:30:49 -0800 [thread overview]
Message-ID: <20190116133049.029292da@shemminger-XPS-13-9360> (raw)
In-Reply-To: <2810348.XpGyddNB5W@xps>
On Wed, 19 Dec 2018 03:37:16 +0100
Thomas Monjalon <thomas@monjalon.net> wrote:
> Hi Stephen,
>
> Can we expect a v2 of this patch? At least for removing deprecation
> and bump ethdev version, etc?
>
> 05/09/2018 18:41, Stephen Hemminger:
> > 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.
> >
> > The initial version sets max mtu to normal Ethernet, it is up to
> > PMD to set larger value if it supports Jumbo frames.
> >
> > Fixing the drivers to use this is trivial and can be done by 18.11.
> > Already have some of the patches done.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
>
>
>
It needs more than just this patch to be worthwhile.
Need device drivers to fill in the max_mtu field, otherwise it would
just break jumbo frame support.
I suppose an initial patch to bump ethdev version would be possible for 19.05,
are there other API changes doing that already for that relaease.
next prev parent reply other threads:[~2019-01-16 21:30 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
2018-12-19 2:37 ` Thomas Monjalon
2019-01-16 21:30 ` Stephen Hemminger [this message]
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=20190116133049.029292da@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
/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).