mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-01 00:48:00 +00:00
zeekay
b61441f7d7
A fork of Rancher's local-path-provisioner at v0.0.36. The behaviour is unchanged and deliberately so — a directory on the node a pod lands on is the right thing for a disk. What changes is identity. The provisioner answers to hanzo.ai/volume rather than rancher.io/local-path. That is not branding: two provisioners sharing one name race for the same claims, and a stock k3s carries the upstream one, so a cluster running both would settle our storage by chance. Data lives at /var/lib/hanzo/volume, so reading a Hanzo cluster does not mean learning another vendor's directory. Apache-2.0 as published, unaltered, with Rancher's attribution in NOTICE. The README says what this is not: durability. A volume here dies with its node. That is hanzoai/replicate's question, one layer up, and keeping the two apart is what lets the disk stay this simple.
34 lines
675 B
Go
34 lines
675 B
Go
//go:build !amd64 || appengine || !gc || noasm
|
|
// +build !amd64 appengine !gc noasm
|
|
|
|
// Copyright 2019+ Klaus Post. All rights reserved.
|
|
// License information can be found in the LICENSE file.
|
|
|
|
package zstd
|
|
|
|
import (
|
|
"encoding/binary"
|
|
"math/bits"
|
|
)
|
|
|
|
// matchLen returns the maximum common prefix length of a and b.
|
|
// a must be the shortest of the two.
|
|
func matchLen(a, b []byte) (n int) {
|
|
for ; len(a) >= 8 && len(b) >= 8; a, b = a[8:], b[8:] {
|
|
diff := binary.LittleEndian.Uint64(a) ^ binary.LittleEndian.Uint64(b)
|
|
if diff != 0 {
|
|
return n + bits.TrailingZeros64(diff)>>3
|
|
}
|
|
n += 8
|
|
}
|
|
|
|
for i := range a {
|
|
if a[i] != b[i] {
|
|
break
|
|
}
|
|
n++
|
|
}
|
|
return n
|
|
|
|
}
|