mirror of https://github.com/minio/minio.git
9d07cde385
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. |
||
---|---|---|
.. | ||
testdata/contrib | ||
amqp.go | ||
common.go | ||
elasticsearch.go | ||
kafka.go | ||
kafka_scram_client_contrib.go | ||
mqtt.go | ||
mysql.go | ||
mysql_test.go | ||
nats.go | ||
nats_contrib_test.go | ||
nats_tls_contrib_test.go | ||
nsq.go | ||
nsq_test.go | ||
postgresql.go | ||
postgresql_test.go | ||
queuestore.go | ||
queuestore_test.go | ||
redis.go | ||
store.go | ||
webhook.go |