The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	George Cherian <gcherian@marvell.com>,
	Huacai Chen <chenhuacai@kernel.org>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] crypto: mips/poly1305 - enable for all MIPS processors
Date: Mon, 8 Mar 2021 11:54:37 +0100	[thread overview]
Message-ID: <20210308105437.GB6622@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2103030122010.19637@angie.orcam.me.uk>

On Wed, Mar 03, 2021 at 02:16:04AM +0100, Maciej W. Rozycki wrote:
> The MIPS Poly1305 implementation is generic MIPS code written such as to 
> support down to the original MIPS I and MIPS III ISA for the 32-bit and 
> 64-bit variant respectively.  Lift the current limitation then to enable 
> code for MIPSr1 ISA or newer processors only and have it available for 
> all MIPS processors.
> 
> Signed-off-by: Maciej W. Rozycki <macro@orcam.me.uk>
> Fixes: a11d055e7a64 ("crypto: mips/poly1305 - incorporate OpenSSL/CRYPTOGAMS optimized implementation")
> Cc: stable@vger.kernel.org # v5.5+
> ---
> On Wed, 3 Mar 2021, Jason A. Donenfeld wrote:
> 
> > >> Would you mind sending this for 5.12 in an rc at some point, rather
> > >> than waiting for 5.13? I'd like to see this backported to 5.10 and 5.4
> > >> for OpenWRT.
> > >
> > > why is this so important for OpenWRT ? Just to select CRYPTO_POLY1305_MIPS
> > > ?
> > 
> > Yes. The performance boost on Octeon is significant for WireGuard users.
> 
>  But that's the wrong fix for that purpose.  I've skimmed over that module 
> and there's nothing MIPS64-specific there.  In fact it's plain generic 
> MIPS assembly, with some R2 optimisations enabled where applicable but not 
> necessary (and then R6 tweaks, but that's irrelevant here).
> 
>  As a matter of interest I have just built it successfully for a MIPS I 
> DECstation configuration:
> 
> $ file arch/mips/crypto/poly1305-mips.ko
> arch/mips/crypto/poly1305-mips.ko: ELF 32-bit LSB relocatable, MIPS, MIPS-I version 1 (SYSV), BuildID[sha1]=d36384d94f60ba7deff638ca8a24500120b45b56, not stripped
> $ 
> 
> Patch included, please apply.
> 
>  So while your change is surely right, what you want is this really.
> 
>   Maciej
> ---
>  arch/mips/crypto/Makefile |    4 ++--
>  crypto/Kconfig            |    2 +-
>  drivers/net/Kconfig       |    2 +-
>  3 files changed, 4 insertions(+), 4 deletions(-)

applied to mips-fixes.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2021-03-08 10:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03  1:16 [PATCH] crypto: mips/poly1305 - enable for all MIPS processors Maciej W. Rozycki
2021-03-03  8:17 ` Jason A. Donenfeld
2021-03-03 12:31   ` Andy Polyakov
2021-03-03 12:32     ` Jason A. Donenfeld
2021-03-08 10:54 ` Thomas Bogendoerfer [this message]

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=20210308105437.GB6622@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=Jason@zx2c4.com \
    --cc=chenhuacai@kernel.org \
    --cc=gcherian@marvell.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=ralf@linux-mips.org \
    --cc=stable@vger.kernel.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: link
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