From: Jakub Kicinski <kuba@kernel•org>
To: Taehee Yoo <ap420073@gmail•com>
Cc: linux-crypto@vger•kernel.org, herbert@gondor•apana.org.au,
davem@davemloft•net, borisp@nvidia•com, john.fastabend@gmail•com,
daniel@iogearbox•net, edumazet@google•com, pabeni@redhat•com,
netdev@vger•kernel.org
Subject: Re: [PATCH v2 3/3] net: tls: Add ARIA-GCM algorithm
Date: Mon, 4 Jul 2022 20:10:09 -0700 [thread overview]
Message-ID: <20220704201009.34fb8aa8@kernel.org> (raw)
In-Reply-To: <20220704094250.4265-4-ap420073@gmail.com>
On Mon, 4 Jul 2022 09:42:50 +0000 Taehee Yoo wrote:
> RFC 6209 describes ARIA for TLS 1.2.
> ARIA-128-GCM and ARIA-256-GCM are defined in RFC 6209.
>
> This patch would offer performance increment and an opportunity for
> hardware offload.
Is it okay if you send the crypto patches now and the TLS support after
the merge window? They go via different trees and we can't take the TLS
patches until we get the crypto stuff in net-next. We could work
something out and create a stable branch that both Herbert and us would
pull but we're getting close to the merge window, perhaps we can just
wait?
next prev parent reply other threads:[~2022-07-05 3:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 9:42 [PATCH v2 0/3] crypto: Introduce ARIA symmetric cipher algorithm Taehee Yoo
2022-07-04 9:42 ` [PATCH v2 1/3] crypto: Implement " Taehee Yoo
2022-07-04 9:42 ` [PATCH v2 2/3] crypto: add ARIA testmgr tests Taehee Yoo
2022-07-04 9:42 ` [PATCH v2 3/3] net: tls: Add ARIA-GCM algorithm Taehee Yoo
2022-07-05 3:10 ` Jakub Kicinski [this message]
2022-07-05 4:29 ` Herbert Xu
2022-07-05 18:31 ` Jakub Kicinski
2022-07-09 22:32 ` [PATCH v2 0/3] crypto: Introduce ARIA symmetric cipher algorithm Eric Biggers
2022-07-10 8:08 ` Taehee Yoo
2022-07-15 8:46 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220704201009.34fb8aa8@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=ap420073@gmail$(echo .)com \
--cc=borisp@nvidia$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=john.fastabend@gmail$(echo .)com \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox