gotosocial/vendor/github.com/docker/go-units/MAINTAINERS

# go-units maintainers file
#
# This file describes who runs the docker/go-units project and how.
# This is a living document - if you see something out of date or missing, speak up!
#
# It is structured to be consumable by both humans and programs.
# To extract its contents programmatically, use any TOML-compliant parser.
#
# This file is compiled into the MAINTAINERS file in docker/opensource.
#
[Org]
	[Org."Core maintainers"]
		people = [
			"akihirosuda",
			"dnephin",
			"thajeztah",
			"vdemeester",
		]

[people]

# A reference list of all people associated with the project.
# All other sections should refer to people by their canonical key
# in the people section.

	# ADD YOURSELF HERE IN ALPHABETICAL ORDER

	[people.akihirosuda]
	Name = "Akihiro Suda"
	Email = "akihiro.suda.cz@hco.ntt.co.jp"
	GitHub = "AkihiroSuda"

	[people.dnephin]
	Name = "Daniel Nephin"
	Email = "dnephin@gmail.com"
	GitHub = "dnephin"
	
	[people.thajeztah]
	Name = "Sebastiaan van Stijn"
	Email = "github@gone.nl"
	GitHub = "thaJeztah"

	[people.vdemeester]
	Name = "Vincent Demeester"
	Email = "vincent@sbr.pm"
	GitHub = "vdemeester"
[feature] Inherit resource limits from cgroups (#1336) 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. 2023-01-17 20:59:04 +00:00			`# go-units maintainers file`
			`#`
			`# This file describes who runs the docker/go-units project and how.`
			`# This is a living document - if you see something out of date or missing, speak up!`
			`#`
			`# It is structured to be consumable by both humans and programs.`
			`# To extract its contents programmatically, use any TOML-compliant parser.`
			`#`
			`# This file is compiled into the MAINTAINERS file in docker/opensource.`
			`#`
			`[Org]`
			`[Org."Core maintainers"]`
			`people = [`
			`"akihirosuda",`
			`"dnephin",`
			`"thajeztah",`
			`"vdemeester",`
			`]`

			`[people]`

			`# A reference list of all people associated with the project.`
			`# All other sections should refer to people by their canonical key`
			`# in the people section.`

			`# ADD YOURSELF HERE IN ALPHABETICAL ORDER`

			`[people.akihirosuda]`
			`Name = "Akihiro Suda"`
			`Email = "akihiro.suda.cz@hco.ntt.co.jp"`
			`GitHub = "AkihiroSuda"`

			`[people.dnephin]`
			`Name = "Daniel Nephin"`
			`Email = "dnephin@gmail.com"`
			`GitHub = "dnephin"`

			`[people.thajeztah]`
			`Name = "Sebastiaan van Stijn"`
			`Email = "github@gone.nl"`
			`GitHub = "thaJeztah"`

			`[people.vdemeester]`
			`Name = "Vincent Demeester"`
			`Email = "vincent@sbr.pm"`
			`GitHub = "vdemeester"`