minio

Commit Graph

Author	SHA1	Message	Date
Klaus Post	a9f1ad7924	Add extended checksum support (#15433 )	2022-08-29 16:57:16 -07:00
Aditya Manthramurthy	be6ccd129d	fix: typo in FIPS sha256 (#15024 )	2022-06-01 19:11:04 -07:00
Harshavardhana	9d07cde385	use crypto/sha256 only for FIPS 140-2 compliance (#14983 ) It would seem like the PR #11623 had chewed more than it wanted to, non-fips build shouldn't really be forced to use slower crypto/sha256 even for presumed "non-performance" codepaths. In MinIO there are really no "non-performance" codepaths. This assumption seems to have had an adverse effect in certain areas of CPU usage. This PR ensures that we stick to sha256-simd on all non-FIPS builds, our most common build to ensure we get the best out of the CPU at any given point in time.	2022-05-27 06:00:19 -07:00

Author

SHA1

Message

Date

Klaus Post

a9f1ad7924

Add extended checksum support (#15433 )

2022-08-29 16:57:16 -07:00

Aditya Manthramurthy

be6ccd129d

fix: typo in FIPS sha256 (#15024 )

2022-06-01 19:11:04 -07:00

Harshavardhana

9d07cde385

use crypto/sha256 only for FIPS 140-2 compliance (#14983 )

It would seem like the PR #11623 had chewed more
than it wanted to, non-fips build shouldn't really
be forced to use slower crypto/sha256 even for
presumed "non-performance" codepaths. In MinIO
there are really no "non-performance" codepaths.
This assumption seems to have had an adverse
effect in certain areas of CPU usage.

This PR ensures that we stick to sha256-simd
on all non-FIPS builds, our most common build
to ensure we get the best out of the CPU at
any given point in time.

2022-05-27 06:00:19 -07:00

3 Commits