[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1507070577.8061.32.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Tue, 03 Oct 2017 15:42:57 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Richard Sailer <richard_siegfried@...temli.org>
Cc: netdev@...r.kernel.org, davem@...emloft.net, kuznet@....inr.ac.ru,
yoshfuji@...ux-ipv6.org
Subject: Re: [PATCH net-next 0/3] A own subdirectory for shared TCP code
On Wed, 2017-10-04 at 00:22 +0200, Richard Sailer wrote:
> net/ipv4 currently contains around 100 source files containing the
> IP implementation and lots of other functionality (UDP, TCP, xfrm, etc.)
>
> # 1/3
> To make the networking source tree more self documenting and well
> structured 1/3 moves the 30 shared TCP source files to a own
> subdirectory of net/ipv4/.
>
> # 2/3
> A huge part of the TCP code is congestion control algorithms.
> With the same goal as above, this moves the cc algos to a own
> subdirectory of net/ipv4/tcp/
>
> # 3/3
> Implementation of a suggestion of valdis, to have a new directory
> net/ipv4v6_shared that contains all the code shared between
> IPv4 and IPv6. This creates net/ipv4v6_shared and moves the
> net/ipv4/tcp directory of shared TCP code there.
>
> While every commit depends on its previous commits, it is
> also possible and sensible to only apply (1) or (1,2) , depending
> on how conservative one wants to decide regarding directory
> structure changes.
>
> [PATCH net-next 1/3] net/ipv4: Move shared tcp code to own subdirectory
> [PATCH net-next 2/3] tcp: Move cc algorithms to own subdirectory
> [PATCH net-next 3/3] Move shared tcp code to net/ipv4v6shared
NACK for the whole series.
Simple reason :
This is going to be a maintenance nightmare, for people dealing with TCP
stack every day.
Powered by blists - more mailing lists