mirror of
https://codeberg.org/superseriousbusiness/gotosocial.git
synced 2024-12-27 03:18:16 +03:00
acc333c40b
When GTS is running in a container runtime which has configured CPU or memory limits or under an init system that uses cgroups to impose CPU and memory limits the values the Go runtime sees for GOMAXPROCS and GOMEMLIMIT are still based on the host resources, not the cgroup. At least for the throttling middlewares which use GOMAXPROCS to configure their queue size, this can result in GTS running with values too big compared to the resources that will actuall be available to it. This introduces 2 dependencies which can pick up resource contraints from the current cgroup and tune the Go runtime accordingly. This should result in the different queues being appropriately sized and in general more predictable performance. These dependencies are a no-op on non-Linux systems or if running in a cgroup that doesn't set a limit on CPU or memory. The automatic tuning of GOMEMLIMIT can be disabled by either explicitly setting GOMEMLIMIT yourself or by setting AUTOMEMLIMIT=off. The automatic tuning of GOMAXPROCS can similarly be counteracted by setting GOMAXPROCS yourself.
54 lines
1.9 KiB
Markdown
54 lines
1.9 KiB
Markdown
# eBPF
|
|
|
|
[](https://pkg.go.dev/github.com/cilium/ebpf)
|
|
|
|
eBPF is a pure Go library that provides utilities for loading, compiling, and
|
|
debugging eBPF programs. It has minimal external dependencies and is intended to
|
|
be used in long running processes.
|
|
|
|
* [asm](https://pkg.go.dev/github.com/cilium/ebpf/asm) contains a basic
|
|
assembler
|
|
* [link](https://pkg.go.dev/github.com/cilium/ebpf/link) allows attaching eBPF
|
|
to various hooks
|
|
* [perf](https://pkg.go.dev/github.com/cilium/ebpf/perf) allows reading from a
|
|
`PERF_EVENT_ARRAY`
|
|
* [cmd/bpf2go](https://pkg.go.dev/github.com/cilium/ebpf/cmd/bpf2go) allows
|
|
embedding eBPF in Go
|
|
|
|
The library is maintained by [Cloudflare](https://www.cloudflare.com) and
|
|
[Cilium](https://www.cilium.io). Feel free to
|
|
[join](https://cilium.herokuapp.com/) the
|
|
[#libbpf-go](https://cilium.slack.com/messages/libbpf-go) channel on Slack.
|
|
|
|
## Current status
|
|
|
|
The package is production ready, but **the API is explicitly unstable right
|
|
now**. Expect to update your code if you want to follow along.
|
|
|
|
## Requirements
|
|
|
|
* A version of Go that is [supported by
|
|
upstream](https://golang.org/doc/devel/release.html#policy)
|
|
* Linux 4.9, 4.19 or 5.4 (versions in-between should work, but are not tested)
|
|
|
|
## Useful resources
|
|
|
|
* [eBPF.io](https://ebpf.io) (recommended)
|
|
* [Cilium eBPF documentation](https://docs.cilium.io/en/latest/bpf/#bpf-guide)
|
|
(recommended)
|
|
* [Linux documentation on
|
|
BPF](https://www.kernel.org/doc/html/latest/networking/filter.html)
|
|
* [eBPF features by Linux
|
|
version](https://github.com/iovisor/bcc/blob/master/docs/kernel-versions.md)
|
|
|
|
## Regenerating Testdata
|
|
|
|
Run `make` in the root of this repository to rebuild testdata in all
|
|
subpackages. This requires Docker, as it relies on a standardized build
|
|
environment to keep the build output stable.
|
|
|
|
The toolchain image build files are kept in [testdata/docker/](testdata/docker/).
|
|
|
|
## License
|
|
|
|
MIT
|