On Tue, 6 Aug 2019 14:56:23 +
Matan Azrad wrote:
> The API breakage is because the ``tso_segsz`` field was documented for
> LRO.
>
> The ``tso_segsz`` field in mbuf indicates the size of each segment in
> the LRO packet in Rx path and should be provided by the LRO packet
> port.
>
> While
On Mon, Jul 27, 2020 at 08:41:47AM +, Matan Azrad wrote:
>
> Hi Olivier
>
> From: Olivier Matz:
> > Hi,
> >
> > On Tue, Jun 02, 2020 at 06:49:01AM +, Matan Azrad wrote:
> > > Hi
> > >
> > > From: Thomas Monjalon
> > > > 10/08/2019 23:31, Thomas Monjalon:
> > > > > 06/08/2019 20:17, Andre
Hi Olivier
From: Olivier Matz:
> Hi,
>
> On Tue, Jun 02, 2020 at 06:49:01AM +, Matan Azrad wrote:
> > Hi
> >
> > From: Thomas Monjalon
> > > 10/08/2019 23:31, Thomas Monjalon:
> > > > 06/08/2019 20:17, Andrew Rybchenko:
> > > > > On 8/6/19 5:56 PM, Matan Azrad wrote:
> > > > > > The API bre
Hi,
On Tue, Jun 02, 2020 at 06:49:01AM +, Matan Azrad wrote:
> Hi
>
> From: Thomas Monjalon
> > 10/08/2019 23:31, Thomas Monjalon:
> > > 06/08/2019 20:17, Andrew Rybchenko:
> > > > On 8/6/19 5:56 PM, Matan Azrad wrote:
> > > > > The API breakage is because the ``tso_segsz`` field was document
Hi
From: Thomas Monjalon
> 10/08/2019 23:31, Thomas Monjalon:
> > 06/08/2019 20:17, Andrew Rybchenko:
> > > On 8/6/19 5:56 PM, Matan Azrad wrote:
> > > > The API breakage is because the ``tso_segsz`` field was documented
> > > > for LRO.
> > > >
> > > > The ``tso_segsz`` field in mbuf indicates th
10/08/2019 23:31, Thomas Monjalon:
> 06/08/2019 20:17, Andrew Rybchenko:
> > On 8/6/19 5:56 PM, Matan Azrad wrote:
> > > The API breakage is because the ``tso_segsz`` field was documented for
> > > LRO.
> > >
> > > The ``tso_segsz`` field in mbuf indicates the size of each segment in
> > > the LRO
06/08/2019 20:17, Andrew Rybchenko:
> On 8/6/19 5:56 PM, Matan Azrad wrote:
> > The API breakage is because the ``tso_segsz`` field was documented for
> > LRO.
> >
> > The ``tso_segsz`` field in mbuf indicates the size of each segment in
> > the LRO packet in Rx path and should be provided by the L
> Hi
> From: Ananyev, Konstantin
> > Hi Matan,
> >
> > > > > > > > >
> > > > > > > > > The API breakage is because the ``tso_segsz`` field was
> > > > > > > > > documented for LRO.
> > > > > > > > >
> > > > > > > > > The ``tso_segsz`` field in mbuf indicates the size of each
> > > > > > > > > se
Hi
From: Ananyev, Konstantin
> Hi Matan,
>
> > > > > > > >
> > > > > > > > The API breakage is because the ``tso_segsz`` field was
> > > > > > > > documented for LRO.
> > > > > > > >
> > > > > > > > The ``tso_segsz`` field in mbuf indicates the size of each
> > > > > > > > segment in the LRO pac
Hi Matan,
> > > > > > >
> > > > > > > The API breakage is because the ``tso_segsz`` field was
> > > > > > > documented for LRO.
> > > > > > >
> > > > > > > The ``tso_segsz`` field in mbuf indicates the size of each
> > > > > > > segment in the LRO packet in Rx path and should be provided by
> > >
From: Ananyev, Konstantin
> > Hi Konstantin
> >
> > From: Ananyev, Konstantin
> > > Sent: Wednesday, August 7, 2019 1:18 PM
> > > To: Matan Azrad ; dev@dpdk.org
> > > Cc: Thomas Monjalon ; Yigit, Ferruh
> > > ; Andrew Rybchenko
> > > ; Olivier Matz
> > > Subject: RE: [PATCH 2/2] doc: announce n
>
> Hi Konstantin
>
> From: Ananyev, Konstantin
> > Sent: Wednesday, August 7, 2019 1:18 PM
> > To: Matan Azrad ; dev@dpdk.org
> > Cc: Thomas Monjalon ; Yigit, Ferruh
> > ; Andrew Rybchenko
> > ; Olivier Matz
> > Subject: RE: [PATCH 2/2] doc: announce new mbuf field for LRO
> >
> > Hi Matan,
Hi Konstantin
From: Ananyev, Konstantin
> Sent: Wednesday, August 7, 2019 1:18 PM
> To: Matan Azrad ; dev@dpdk.org
> Cc: Thomas Monjalon ; Yigit, Ferruh
> ; Andrew Rybchenko
> ; Olivier Matz
> Subject: RE: [PATCH 2/2] doc: announce new mbuf field for LRO
>
> Hi Matan,
>
> > > >
> > > > The AP
Hi Matan,
> > >
> > > The API breakage is because the ``tso_segsz`` field was documented for
> > > LRO.
> > >
> > > The ``tso_segsz`` field in mbuf indicates the size of each segment in
> > > the LRO packet in Rx path and should be provided by the LRO packet
> > > port.
> > >
> > > While the gener
Hi
From: Ananyev, Konstantin
> > -Original Message-
> > From: Matan Azrad [mailto:ma...@mellanox.com]
> > Sent: Tuesday, August 6, 2019 3:56 PM
> > To: dev@dpdk.org
> > Cc: Thomas Monjalon ; Yigit, Ferruh
> > ; Andrew Rybchenko
> > ; Ananyev, Konstantin
> > ; Olivier Matz
> > Subject: [PA
On 8/6/19 5:56 PM, Matan Azrad wrote:
The API breakage is because the ``tso_segsz`` field was documented for
LRO.
The ``tso_segsz`` field in mbuf indicates the size of each segment in
the LRO packet in Rx path and should be provided by the LRO packet
port.
While the generic LRO packet may aggre
> -Original Message-
> From: Matan Azrad [mailto:ma...@mellanox.com]
> Sent: Tuesday, August 6, 2019 3:56 PM
> To: dev@dpdk.org
> Cc: Thomas Monjalon ; Yigit, Ferruh
> ; Andrew Rybchenko ;
> Ananyev, Konstantin ; Olivier Matz
>
> Subject: [PATCH 2/2] doc: announce new mbuf field for L
The API breakage is because the ``tso_segsz`` field was documented for
LRO.
The ``tso_segsz`` field in mbuf indicates the size of each segment in
the LRO packet in Rx path and should be provided by the LRO packet
port.
While the generic LRO packet may aggregate different segments sizes in
one pac
18 matches
Mail list logo
