minio

Commit Graph

Author	SHA1	Message	Date
Harshavardhana	d0a0eb9738	support fan-out objects via PostUpload() (#17233 )	2023-05-24 22:51:07 -07:00
Klaus Post	5677f73794	Add PostObject Checksum (#17244 )	2023-05-23 07:58:33 -07:00
Klaus Post	aaf1abc993	simplify HardLimitReader by using LimitReader for internal usage (#17218 )	2023-05-16 13:14:37 -07:00
Harshavardhana	ef2fc0f99e	fix: reduce using memory and temporary files. (#17206 )	2023-05-15 14:08:54 -07:00
Poorna	e07c2ab868	Use hash.NewLimitReader for internal multipart calls (#17191 )	2023-05-12 11:19:08 -07:00
Klaus Post	76913a9fd5	Signed trailers for signature v4 (#16484 )	2023-05-05 19:53:12 -07:00
Harshavardhana	328d660106	support CRC32 Checksums on single drive setup (#15873 )	2022-10-15 11:58:47 -07:00
Klaus Post	a9f1ad7924	Add extended checksum support (#15433 )	2022-08-29 16:57:16 -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
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

10 Commits