From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, will.deacon@arm.com,
catalin.marinas@arm.com, herbert@gondor.apana.org.au,
ebiggers@google.com, suzuki.poulose@arm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] arm64: wire CRC32 instructions into core crc32 routines
Date: Mon, 27 Aug 2018 10:53:52 -0400 [thread overview]
Message-ID: <20180827145352.GF2311@thunk.org> (raw)
In-Reply-To: <20180827110245.14812-1-ard.biesheuvel@linaro.org>
On Mon, Aug 27, 2018 at 01:02:41PM +0200, Ard Biesheuvel wrote:
> While this is not known to cause performance issues, calling a table based
> time variant implementation with a non-negligible D-cache footprint (8 KB)
> is wasteful in any case, and now that the crc32 instructions have been made
> mandatory in the architecture, let's wire them up into the core crc routines.
Stupid question --- are there any arm64 SOC's out there which do *not*
have the crc32 instructions? Presumably there won't be in the future,
because it's now mandatory --- but where there any in the past?
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: tytso@mit.edu (Theodore Y. Ts'o)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] arm64: wire CRC32 instructions into core crc32 routines
Date: Mon, 27 Aug 2018 10:53:52 -0400 [thread overview]
Message-ID: <20180827145352.GF2311@thunk.org> (raw)
In-Reply-To: <20180827110245.14812-1-ard.biesheuvel@linaro.org>
On Mon, Aug 27, 2018 at 01:02:41PM +0200, Ard Biesheuvel wrote:
> While this is not known to cause performance issues, calling a table based
> time variant implementation with a non-negligible D-cache footprint (8 KB)
> is wasteful in any case, and now that the crc32 instructions have been made
> mandatory in the architecture, let's wire them up into the core crc routines.
Stupid question --- are there any arm64 SOC's out there which do *not*
have the crc32 instructions? Presumably there won't be in the future,
because it's now mandatory --- but where there any in the past?
- Ted
next prev parent reply other threads:[~2018-08-27 14:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 11:02 [PATCH 0/4] arm64: wire CRC32 instructions into core crc32 routines Ard Biesheuvel
2018-08-27 11:02 ` Ard Biesheuvel
2018-08-27 11:02 ` [PATCH 1/4] lib/crc32: make core crc32() routines weak so they can be overridden Ard Biesheuvel
2018-08-27 11:02 ` Ard Biesheuvel
2018-09-04 9:44 ` Herbert Xu
2018-09-04 9:44 ` Herbert Xu
2018-09-04 9:44 ` Herbert Xu
2018-08-27 11:02 ` [PATCH 2/4] arm64: cpufeature: add feature for CRC32 instructions Ard Biesheuvel
2018-08-27 11:02 ` Ard Biesheuvel
2018-08-28 17:01 ` Will Deacon
2018-08-28 17:01 ` Will Deacon
2018-08-28 18:43 ` Ard Biesheuvel
2018-08-28 18:43 ` Ard Biesheuvel
2018-09-04 3:18 ` Herbert Xu
2018-09-04 3:18 ` Herbert Xu
2018-09-04 9:38 ` Will Deacon
2018-09-04 9:38 ` Will Deacon
2018-09-04 9:44 ` Herbert Xu
2018-09-04 9:44 ` Herbert Xu
2018-09-10 15:45 ` Catalin Marinas
2018-09-10 15:45 ` Catalin Marinas
2018-08-27 11:02 ` [PATCH 3/4] arm64/lib: add accelerated crc32 routines Ard Biesheuvel
2018-08-27 11:02 ` Ard Biesheuvel
2018-08-27 11:02 ` [PATCH 4/4] crypto: arm64/crc32 - remove PMULL based CRC32 driver Ard Biesheuvel
2018-08-27 11:02 ` Ard Biesheuvel
2018-09-04 5:21 ` Herbert Xu
2018-09-04 5:21 ` Herbert Xu
2018-08-27 14:53 ` Theodore Y. Ts'o [this message]
2018-08-27 14:53 ` [PATCH 0/4] arm64: wire CRC32 instructions into core crc32 routines Theodore Y. Ts'o
2018-08-27 15:18 ` Ard Biesheuvel
2018-08-27 15:18 ` Ard Biesheuvel
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=20180827145352.GF2311@thunk.org \
--to=tytso@mit.edu \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@arm.com \
/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 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.