mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-30 14:55:30 +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.
38 lines
892 B
Go
38 lines
892 B
Go
// Copyright 2019 The Go Authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style
|
|
// license that can be found in the LICENSE file.
|
|
|
|
//go:build race
|
|
|
|
package socket
|
|
|
|
import (
|
|
"runtime"
|
|
"unsafe"
|
|
)
|
|
|
|
// This package reads and writes the Message buffers using a
|
|
// direct system call, which the race detector can't see.
|
|
// These functions tell the race detector what is going on during the syscall.
|
|
|
|
func (m *Message) raceRead() {
|
|
for _, b := range m.Buffers {
|
|
if len(b) > 0 {
|
|
runtime.RaceReadRange(unsafe.Pointer(&b[0]), len(b))
|
|
}
|
|
}
|
|
if b := m.OOB; len(b) > 0 {
|
|
runtime.RaceReadRange(unsafe.Pointer(&b[0]), len(b))
|
|
}
|
|
}
|
|
func (m *Message) raceWrite() {
|
|
for _, b := range m.Buffers {
|
|
if len(b) > 0 {
|
|
runtime.RaceWriteRange(unsafe.Pointer(&b[0]), len(b))
|
|
}
|
|
}
|
|
if b := m.OOB; len(b) > 0 {
|
|
runtime.RaceWriteRange(unsafe.Pointer(&b[0]), len(b))
|
|
}
|
|
}
|