]> git.ipfire.org Git - thirdparty/squid.git/commit - src/SquidConfig.h
Do not use invasive lists to store CachePeers (#1424)
authorEduard Bagdasaryan <eduard.bagdasaryan@measurement-factory.com>
Thu, 31 Aug 2023 23:00:01 +0000 (23:00 +0000)
committerSquid Anubis <squid-anubis@squid-cache.org>
Tue, 5 Sep 2023 21:47:25 +0000 (21:47 +0000)
commit2e24d0bfa7c8329f56607b0c7d041a61542d344a
tree5697ba14658e5036d2f6566e4fc85de019bf2351
parent3e50f1af739a198888309ba48dee0a7044fbf0b1
Do not use invasive lists to store CachePeers (#1424)

Using invasive lists for CachePeer objects gives no advantages, but
requires maintaining non-standard error-prone code that leads to
excessive locking and associated memory overheads.

Also fixed a neighbors_init() bug that resulted in accessing an already
deleted "looks like this host" CachePeer object.
19 files changed:
src/CachePeer.cc
src/CachePeer.h
src/CachePeers.cc [new file with mode: 0644]
src/CachePeers.h
src/Makefile.am
src/PeerPoolMgr.cc
src/SquidConfig.h
src/cache_cf.cc
src/carp.cc
src/htcp.cc
src/icmp/net_db.cc
src/neighbors.cc
src/neighbors.h
src/peer_select.cc
src/peer_sourcehash.cc
src/peer_userhash.cc
src/snmp_agent.cc
src/snmp_core.cc
src/stat.cc