Harshavardhana 4550ac6fff fix: refactor locks to apply them uniquely per node (#11052) ... This refactor is done for few reasons below - to avoid deadlocks in scenarios when number of nodes are smaller < actual erasure stripe count where in N participating local lockers can lead to deadlocks across systems. - avoids expiry routines to run 1000 of separate network operations and routes per disk where as each of them are still accessing one single local entity. - it is ideal to have since globalLockServer per instance. - In a 32node deployment however, each server group is still concentrated towards the same set of lockers that partipicate during the write/read phase, unlike previous minio/dsync implementation - this potentially avoids send 32 requests instead we will still send at max requests of unique nodes participating in a write/read phase. - reduces overall chattiness on smaller setups.		2020-12-10 07:28:37 -08:00
..
argon2_test.go	use argon2 with sync.Pool for better memory management (#11019)	2020-12-03 19:23:19 -08:00
argon2.go	fix: refactor locks to apply them uniquely per node (#11052)	2020-12-10 07:28:37 -08:00
blake2b.go	use argon2 with sync.Pool for better memory management (#11019)	2020-12-03 19:23:19 -08:00
blamka_amd64.go	use argon2 with sync.Pool for better memory management (#11019)	2020-12-03 19:23:19 -08:00
blamka_amd64.s	use argon2 with sync.Pool for better memory management (#11019)	2020-12-03 19:23:19 -08:00
blamka_generic.go	use argon2 with sync.Pool for better memory management (#11019)	2020-12-03 19:23:19 -08:00
blamka_ref.go	use argon2 with sync.Pool for better memory management (#11019)	2020-12-03 19:23:19 -08:00