minio

Commit Graph

Author	SHA1	Message	Date
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
Harshavardhana	202d0b64eb	fix: enable go1.17 github ci/cd (#12997 )	2021-08-18 18:35:22 -07:00
Harshavardhana	1f262daf6f	rename all remaining packages to internal/ (#12418 ) This is to ensure that there are no projects that try to import `minio/minio/pkg` into their own repo. Any such common packages should go to `https://github.com/minio/pkg`	2021-06-01 14:59:40 -07:00

Author

SHA1

Message

Date

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

Harshavardhana

202d0b64eb

fix: enable go1.17 github ci/cd (#12997 )

2021-08-18 18:35:22 -07:00

Harshavardhana

1f262daf6f

rename all remaining packages to internal/ (#12418 )

This is to ensure that there are no projects
that try to import `minio/minio/pkg` into
their own repo. Any such common packages should
go to `https://github.com/minio/pkg`

2021-06-01 14:59:40 -07:00

3 Commits