From: "Horia Geantă" <horia.geanta@nxp.com> To: Herbert Xu <herbert@gondor.apana.org.au>, Christophe Leroy <christophe.leroy@c-s.fr> Cc: "David S. Miller" <davem@davemloft.net>, "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org> Subject: Re: [PATCH 00/18] crypto: talitos - fixes and performance improvement Date: Fri, 8 Dec 2017 15:20:40 +0000 [thread overview] Message-ID: <VI1PR0402MB3342A19DE16BEEB714DAA98A98300@VI1PR0402MB3342.eurprd04.prod.outlook.com> (raw) In-Reply-To: 20171012151959.GI31122@gondor.apana.org.au On 10/12/2017 6:20 PM, Herbert Xu wrote: > On Fri, Oct 06, 2017 at 03:04:31PM +0200, Christophe Leroy wrote: >> This serie fixes and improves the talitos crypto driver. >> >> First 6 patchs are fixes of failures reported by the new tests in the >> kernel crypto test manager. >> Looks like these fixes are required also on older 4.9+ -stable kernels. (I haven't seen them on latest 4.9.68-stable mail from Greg, even though they are in main tree.) In case you agree, what would be the recommended way to add the patches to -stable? Thanks, Horia >> The 8 following patches are cleanups and simplifications. >> >> The last 4 ones are performance improvement. The main improvement is >> in the one before the last, it divides by 2 the time needed for a md5 >> hash on the SEC1. >> >> Christophe Leroy (18): >> crypto: talitos - fix AEAD test failures >> crypto: talitos - fix memory corruption on SEC2 >> crypto: talitos - fix setkey to check key weakness >> crypto: talitos - fix AEAD for sha224 on non sha224 capable chips >> crypto: talitos - fix use of sg_link_tbl_len >> crypto: talitos - fix ctr-aes-talitos >> crypto: talitos - zeroize the descriptor with memset() >> crypto: talitos - declare local functions static >> crypto: talitos - use devm_kmalloc() >> crypto: talitos - use of_property_read_u32() >> crypto: talitos - use devm_ioremap() >> crypto: talitos - don't check the number of channels at each interrupt >> crypto: talitos - remove to_talitos_ptr_len() >> crypto: talitos - simplify tests in ipsec_esp() >> crypto: talitos - DMA map key in setkey() >> crypto: talitos - do hw_context DMA mapping outside the requests >> crypto: talitos - chain in buffered data for ahash on SEC1 >> crypto: talitos - avoid useless copy > > All applied. Thanks. >
WARNING: multiple messages have this Message-ID (diff)
From: "Horia Geantă" <horia.geanta@nxp.com> To: Herbert Xu <herbert@gondor.apana.org.au>, Christophe Leroy <christophe.leroy@c-s.fr> Cc: "David S. Miller" <davem@davemloft.net>, "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org> Subject: Re: [PATCH 00/18] crypto: talitos - fixes and performance improvement Date: Fri, 8 Dec 2017 15:20:40 +0000 [thread overview] Message-ID: <VI1PR0402MB3342A19DE16BEEB714DAA98A98300@VI1PR0402MB3342.eurprd04.prod.outlook.com> (raw) In-Reply-To: 20171012151959.GI31122@gondor.apana.org.au On 10/12/2017 6:20 PM, Herbert Xu wrote:=0A= > On Fri, Oct 06, 2017 at 03:04:31PM +0200, Christophe Leroy wrote:=0A= >> This serie fixes and improves the talitos crypto driver.=0A= >>=0A= >> First 6 patchs are fixes of failures reported by the new tests in the=0A= >> kernel crypto test manager.=0A= >>=0A= Looks like these fixes are required also on older 4.9+ -stable kernels.=0A= (I haven't seen them on latest 4.9.68-stable mail from Greg, even though=0A= they are in main tree.)=0A= =0A= In case you agree, what would be the recommended way to add the patches=0A= to -stable?=0A= =0A= Thanks,=0A= Horia=0A= =0A= >> The 8 following patches are cleanups and simplifications.=0A= >>=0A= >> The last 4 ones are performance improvement. The main improvement is=0A= >> in the one before the last, it divides by 2 the time needed for a md5=0A= >> hash on the SEC1.=0A= >>=0A= >> Christophe Leroy (18):=0A= >> crypto: talitos - fix AEAD test failures=0A= >> crypto: talitos - fix memory corruption on SEC2=0A= >> crypto: talitos - fix setkey to check key weakness=0A= >> crypto: talitos - fix AEAD for sha224 on non sha224 capable chips=0A= >> crypto: talitos - fix use of sg_link_tbl_len=0A= >> crypto: talitos - fix ctr-aes-talitos=0A= >> crypto: talitos - zeroize the descriptor with memset()=0A= >> crypto: talitos - declare local functions static=0A= >> crypto: talitos - use devm_kmalloc()=0A= >> crypto: talitos - use of_property_read_u32()=0A= >> crypto: talitos - use devm_ioremap()=0A= >> crypto: talitos - don't check the number of channels at each interrupt= =0A= >> crypto: talitos - remove to_talitos_ptr_len()=0A= >> crypto: talitos - simplify tests in ipsec_esp()=0A= >> crypto: talitos - DMA map key in setkey()=0A= >> crypto: talitos - do hw_context DMA mapping outside the requests=0A= >> crypto: talitos - chain in buffered data for ahash on SEC1=0A= >> crypto: talitos - avoid useless copy=0A= > =0A= > All applied. Thanks.=0A= > =0A=
next prev parent reply other threads:[~2017-12-08 15:20 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-06 13:04 [PATCH 00/18] crypto: talitos - fixes and performance improvement Christophe Leroy 2017-10-06 13:04 ` [PATCH 01/18] crypto: talitos - fix AEAD test failures Christophe Leroy 2017-10-06 13:04 ` [PATCH 02/18] crypto: talitos - fix memory corruption on SEC2 Christophe Leroy 2017-10-06 13:04 ` [PATCH 03/18] crypto: talitos - fix setkey to check key weakness Christophe Leroy 2017-10-06 13:04 ` [PATCH 04/18] crypto: talitos - fix AEAD for sha224 on non sha224 capable chips Christophe Leroy 2017-10-06 13:04 ` [PATCH 05/18] crypto: talitos - fix use of sg_link_tbl_len Christophe Leroy 2017-10-06 13:04 ` [PATCH 06/18] crypto: talitos - fix ctr-aes-talitos Christophe Leroy 2017-10-06 13:04 ` [PATCH 07/18] crypto: talitos - zeroize the descriptor with memset() Christophe Leroy 2017-10-06 13:04 ` [PATCH 08/18] crypto: talitos - declare local functions static Christophe Leroy 2017-10-06 13:04 ` [PATCH 09/18] crypto: talitos - use devm_kmalloc() Christophe Leroy 2017-10-06 13:04 ` [PATCH 10/18] crypto: talitos - use of_property_read_u32() Christophe Leroy 2017-10-06 13:04 ` [PATCH 11/18] crypto: talitos - use devm_ioremap() Christophe Leroy 2017-10-06 13:04 ` [PATCH 12/18] crypto: talitos - don't check the number of channels at each interrupt Christophe Leroy 2017-10-06 13:04 ` [PATCH 13/18] crypto: talitos - remove to_talitos_ptr_len() Christophe Leroy 2017-10-06 13:04 ` [PATCH 14/18] crypto: talitos - simplify tests in ipsec_esp() Christophe Leroy 2017-10-06 13:05 ` [PATCH 15/18] crypto: talitos - DMA map key in setkey() Christophe Leroy 2017-10-06 13:05 ` [PATCH 16/18] crypto: talitos - do hw_context DMA mapping outside the requests Christophe Leroy 2018-02-07 14:39 ` Horia Geantă 2018-02-07 14:39 ` Horia Geantă 2018-02-17 16:32 ` Christophe LEROY 2018-02-18 17:14 ` Horia Geantă 2018-02-18 17:14 ` Horia Geantă 2018-02-19 7:58 ` Christophe LEROY 2018-02-19 7:58 ` Christophe LEROY 2018-02-19 8:30 ` Horia Geantă 2018-02-19 8:30 ` Horia Geantă 2018-02-19 8:30 ` Horia Geantă 2018-02-19 9:14 ` Christophe LEROY 2018-02-19 9:14 ` Christophe LEROY 2018-02-19 13:16 ` Horia Geantă 2018-02-19 13:16 ` Horia Geantă 2018-02-19 13:16 ` Horia Geantă 2018-02-20 10:34 ` Herbert Xu 2018-02-20 10:34 ` Herbert Xu 2018-02-20 11:32 ` Horia Geantă 2018-02-20 11:32 ` Horia Geantă 2018-02-20 11:32 ` Horia Geantă 2018-02-22 11:47 ` Herbert Xu 2018-02-22 11:47 ` Herbert Xu 2018-02-22 12:29 ` Horia Geantă 2018-02-22 12:29 ` Horia Geantă 2018-02-22 12:29 ` Horia Geantă 2018-02-22 13:46 ` Herbert Xu 2018-02-22 13:46 ` Herbert Xu 2017-10-06 13:05 ` [PATCH 17/18] crypto: talitos - chain in buffered data for ahash on SEC1 Christophe Leroy 2018-03-02 17:27 ` Horia Geantă 2018-03-02 17:27 ` Horia Geantă 2018-03-02 17:42 ` Christophe LEROY 2017-10-06 13:05 ` [PATCH 18/18] crypto: talitos - avoid useless copy Christophe Leroy 2017-10-12 15:19 ` [PATCH 00/18] crypto: talitos - fixes and performance improvement Herbert Xu 2017-12-08 15:20 ` Horia Geantă [this message] 2017-12-08 15:20 ` Horia Geantă 2017-12-11 11:07 ` 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=VI1PR0402MB3342A19DE16BEEB714DAA98A98300@VI1PR0402MB3342.eurprd04.prod.outlook.com \ --to=horia.geanta@nxp.com \ --cc=christophe.leroy@c-s.fr \ --cc=davem@davemloft.net \ --cc=herbert@gondor.apana.org.au \ --cc=linux-crypto@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.