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.
35 lines
820 B
Go
35 lines
820 B
Go
// Package cpuinfo gives runtime info about the current CPU.
|
|
//
|
|
// This is a very limited module meant for use internally
|
|
// in this project. For more versatile solution check
|
|
// https://github.com/klauspost/cpuid.
|
|
package cpuinfo
|
|
|
|
// HasBMI1 checks whether an x86 CPU supports the BMI1 extension.
|
|
func HasBMI1() bool {
|
|
return hasBMI1
|
|
}
|
|
|
|
// HasBMI2 checks whether an x86 CPU supports the BMI2 extension.
|
|
func HasBMI2() bool {
|
|
return hasBMI2
|
|
}
|
|
|
|
// DisableBMI2 will disable BMI2, for testing purposes.
|
|
// Call returned function to restore previous state.
|
|
func DisableBMI2() func() {
|
|
old := hasBMI2
|
|
hasBMI2 = false
|
|
return func() {
|
|
hasBMI2 = old
|
|
}
|
|
}
|
|
|
|
// HasBMI checks whether an x86 CPU supports both BMI1 and BMI2 extensions.
|
|
func HasBMI() bool {
|
|
return HasBMI1() && HasBMI2()
|
|
}
|
|
|
|
var hasBMI1 bool
|
|
var hasBMI2 bool
|