Aaron Lehmann b642b3f21f Avoid using a map for log attributes ... Having a map per log entry seemed heavier than necessary. These attributes end up being sorted and serialized, so storing them in a map doesn't add anything (there's no random access element). In SwarmKit, they originate as a slice, so there's an unnecessary conversion to a map and back. This also fixes the sort comparator, which used to inefficiently split the string on each comparison. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2017-07-18 19:01:20 -07:00
..
controllers/plugin	Make plugin emit strongly typed, consumable events	2017-07-06 14:26:06 -04:00
convert	pluggable secret backend	2017-07-15 16:50:02 +03:00
executor	Avoid using a map for log attributes	2017-07-18 19:01:20 -07:00
provider
cluster.go	Make plugin emit strongly typed, consumable events	2017-07-06 14:26:06 -04:00
configs.go
filters.go	Make plugin emit strongly typed, consumable events	2017-07-06 14:26:06 -04:00
filters_test.go
helpers.go
listen_addr.go
listen_addr_linux.go
listen_addr_others.go
listen_addr_solaris.go
networks.go
noderunner.go	make engine support cluster config event	2017-07-11 17:21:15 +08:00
nodes.go
secrets.go
services.go	Avoid using a map for log attributes	2017-07-18 19:01:20 -07:00
swarm.go	Do not clear swarm directory at the begining of swarm init and swarm join now.	2017-05-22 17:45:20 -07:00
tasks.go	Make plugin emit strongly typed, consumable events	2017-07-06 14:26:06 -04:00
utils.go