> > The same issue was fixed on for the ipv4 version of this routine in
> > commit 8d4d3a4f7337 ("ip_frag: handle MTU sizes not aligned to 8 bytes").
> > Briefly, the size of an ipv6 header is always 40 bytes. With an MTU of
> > 1500, this will never produce a multiple of 8 bytes for the frag_size
> -Original Message-
> From: Chas Williams [mailto:3ch...@gmail.com]
> Sent: Tuesday, November 27, 2018 4:56 AM
> To: dev@dpdk.org
> Cc: Ananyev, Konstantin ; Chas Williams
>
> Subject: [PATCH] ip_frag: fix ipv6 when MTU sizes not aligned to 8 bytes
>
> From: Chas Williams
>
> The s
28/11/2018 11:15, Luca Boccassi:
> On Mon, 2018-11-26 at 23:56 -0500, Chas Williams wrote:
> > From: Chas Williams
> >
> > The same issue was fixed on for the ipv4 version of this routine in
> > commit 8d4d3a4f7337 ("ip_frag: handle MTU sizes not aligned to 8
> > bytes").
> > Briefly, the size of
On Mon, 2018-11-26 at 23:56 -0500, Chas Williams wrote:
> From: Chas Williams
>
> The same issue was fixed on for the ipv4 version of this routine in
> commit 8d4d3a4f7337 ("ip_frag: handle MTU sizes not aligned to 8
> bytes").
> Briefly, the size of an ipv6 header is always 40 bytes. With an MT
From: Chas Williams
The same issue was fixed on for the ipv4 version of this routine in
commit 8d4d3a4f7337 ("ip_frag: handle MTU sizes not aligned to 8 bytes").
Briefly, the size of an ipv6 header is always 40 bytes. With an MTU of
1500, this will never produce a multiple of 8 bytes for the fra
5 matches
Mail list logo
