netdev - Re: [PATCH net-next v1] gso: Support partial splitting at the frag

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 29 Aug 2016 14:02:31 +0200
From:   Steffen Klassert <steffen.klassert@...unet.com>
To:     Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
CC:     Alexander Duyck <alexander.duyck@...il.com>,
        Netdev <netdev@...r.kernel.org>,
        Eric Dumazet <eric.dumazet@...il.com>,
        "Alexander Duyck" <alexander.h.duyck@...el.com>
Subject: Re: [PATCH net-next v1] gso: Support partial splitting at the
 frag_list pointer

On Thu, Aug 25, 2016 at 09:17:18AM -0300, Marcelo Ricardo Leitner wrote:
> On Thu, Aug 25, 2016 at 09:31:26AM +0200, Steffen Klassert wrote:
> > 
> > Just to understand what you are doing. You generate MTU sized linear
> > buffers in sctp and then, skb_gro_receive() chains up these buffers
> > at the frag_list pointer. skb_gro_receive() does this because
> > skb_gro_offset is null and skb->head_frag is not set in your case.
> > 
> > At segmentation, you just need to split at the frag_list pointer
> > because you know that the chained buffers fit the MTU, right?
> > 
> 
> Correct. Just note that these buffers fit the MTU, but not necessary
> uses all of it. That is main point in here, variable segmentation size.

Thanks for the info. This is a very interesting concept, maybe I can use
it for IPsec too.