Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <5618b5e8-4ada-7d08-b7af-178a862f452b@arista.com>
Date:   Tue, 1 Nov 2022 17:35:41 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.3.3
Subject: Re: [PATCH v3 00/36] net/tcp: Add TCP-AO support
Content-Language: en-US
To:     David Ahern <dsahern@kernel.org>, linux-kernel@vger.kernel.org,
        Eric Dumazet <edumazet@google.com>
Cc:     Andy Lutomirski <luto@amacapital.net>,
        Ard Biesheuvel <ardb@kernel.org>,
        Bob Gilligan <gilligan@arista.com>,
        Dan Carpenter <dan.carpenter@oracle.com>,
        "David S. Miller" <davem@davemloft.net>,
        Dmitry Safonov <0x7f454c46@gmail.com>,
        Eric Biggers <ebiggers@kernel.org>,
        "Eric W. Biederman" <ebiederm@xmission.com>,
        Francesco Ruggeri <fruggeri@arista.com>,
        Herbert Xu <herbert@gondor.apana.org.au>,
        Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
        Ivan Delalande <colona@arista.com>,
        Jakub Kicinski <kuba@kernel.org>,
        Leonard Crestez <cdleonard@gmail.com>,
        Paolo Abeni <pabeni@redhat.com>,
        Salam Noureddine <noureddine@arista.com>,
        Shuah Khan <shuah@kernel.org>, netdev@vger.kernel.org,
        linux-crypto@vger.kernel.org
References: <20221027204347.529913-1-dima@arista.com>
 <c0b6c5f1-9b4f-2d3d-69fd-533daa023e09@kernel.org>
From:   Dmitry Safonov <dima@arista.com>
In-Reply-To: <c0b6c5f1-9b4f-2d3d-69fd-533daa023e09@kernel.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi David,

On 11/1/22 02:22, David Ahern wrote:
> Thinking about how to move the TCP-AO intent forward: clearly a 36-patch
> set is a bit much. The first 6 patches are prep work, and we know there
> is a use case for those.
> 
> We could handle patches 3 and 4 as a stand alone set first.
> 
> Once merged, deal with the crypto API and users until those maintainers
> are good. That would be patches 1, 2, 5 and 6.
> 
> Once those are merged it drops down to just networking patches with
> selftests. Those can be split into AO (19) and selftests (11) making it
> 4 total sets of manageable size.
> 
> The AO patches can be reviewed until convergence on a good starting point.
> 
> Sound reasonable?

That sounds reasonable to me.
I'll submit patches 3 & 4 for review and then, once merged, 1, 2, 5 and
6. And later (re)-base TCP-AO on linux-next.

Thanks,
          Dmitry