ndrew Rybchenko
Subject: Re: [dpdk-dev] [RFC] ethdev: add min/max MTU to device info
On 2/7/2019 12:00 PM, Ananyev, Konstantin wrote:
>
>>> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
>>> Konstantin
>>>>
>>>>> From: dev on beha
On 2/7/2019 12:00 PM, Ananyev, Konstantin wrote:
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
Konstantin
From: dev on behalf of Stephen Hemminger
On Wed, 6 Feb 2019 14:05:34 +0100
Morten Brørup wrote:
Good work, Stephen.
It should also be documented how PMDs should inter
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > Konstantin
> > >
> > > > From: dev on behalf of Stephen Hemminger
> > > > On Wed, 6 Feb 2019 14:05:34 +0100
> > > > Morten Brørup wrote:
> > > >
> > > > > Good work, Stephen.
> > > > >
> > > > > It should also be documented how
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> Konstantin
> >
> > > From: dev on behalf of Stephen Hemminger
> > > On Wed, 6 Feb 2019 14:05:34 +0100
> > > Morten Brørup wrote:
> > >
> > > > Good work, Stephen.
> > > >
> > > > It should also be documented how PMDs should interpre
>
> > From: dev on behalf of Stephen Hemminger
> > On Wed, 6 Feb 2019 14:05:34 +0100
> > Morten Brørup wrote:
> >
> > > Good work, Stephen.
> > >
> > > It should also be documented how PMDs should interpret this MTU.
> > >
> > > Obviously, a VLAN tagged Ethernet frame grows from 1518 to 1522 b
> From: dev on behalf of Stephen Hemminger
> On Wed, 6 Feb 2019 14:05:34 +0100
> Morten Brørup wrote:
>
> > Good work, Stephen.
> >
> > It should also be documented how PMDs should interpret this MTU.
> >
> > Obviously, a VLAN tagged Ethernet frame grows from 1518 to 1522 bytes incl.
> > heade
On Wed, 6 Feb 2019 14:05:34 +0100
Morten Brørup wrote:
> Good work, Stephen.
>
> It should also be documented how PMDs should interpret this MTU.
>
> Obviously, a VLAN tagged Ethernet frame grows from 1518 to 1522 bytes incl.
> header and CRC, and should be allowed with an Ethernet MTU of 1500
Good work, Stephen.
It should also be documented how PMDs should interpret this MTU.
Obviously, a VLAN tagged Ethernet frame grows from 1518 to 1522 bytes incl.
header and CRC, and should be allowed with an Ethernet MTU of 1500 bytes.
There's even a #define ETHER_MAX_VLAN_FRAME_LEN for this, bu
On Wed, 19 Dec 2018 03:37:16 +0100
Thomas Monjalon 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
> > sum
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
> 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
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
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
Wednesday, September 5, 2018 7:42 PM, Stephen Hemminger:
> Subject: [dpdk-dev] [RFC] ethdev: add min/max MTU to device info
>
> 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
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 sup
15 matches
Mail list logo
