Fix: RM: Improve init RM message and fix final memory value.

[ajnavarro]

Improved init message explaining what RM is doing. Output example:

Initializing daemon...
Kubo version: 0.18.0-dev-a3913d9f9-dirty
Repo version: 12
System version: amd64/linux
Golang version: go1.19.3

Computing default go-libp2p Resource Manager limits based on: 
    - 'Swarm.ResourceMgr.MaxMemory': "8GB"
    - 'Swarm.ResourceMgr.MaxFileDescriptors': 524288

Applying any user-supplied overrides on top.
Run 'ipfs swarm limit all' to see the resulting limits.

Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip4/127.0.0.1/udp/4001/quic
Swarm listening on /ip4/16.0.0.1/tcp/4001
Swarm listening on /ip4/16.0.0.1/udp/4001/quic
Swarm listening on /ip4/16.1.0.1/tcp/4001
Swarm listening on /ip4/16.1.0.1/udp/4001/quic
Swarm listening on /ip4/16.10.0.1/tcp/4001
Swarm listening on /ip4/16.10.0.1/udp/4001/quic
Swarm listening on /ip4/16.11.0.1/tcp/4001
Swarm listening on /ip4/16.11.0.1/udp/4001/quic
Swarm listening on /ip4/16.12.0.1/tcp/4001
Swarm listening on /ip4/16.12.0.1/udp/4001/quic

Also fixed the computed memory value. When calling Scale(int64(maxMemory), int(numFD)) method we were adding that memory to the previously configured one at System level. Setting System memory and FD to libp2p default ones. Output example using 8GB as set memory now:

ipfs swarm limit system
{
  "Conns": 4611686018427388000,
  "ConnsInbound": 540,
  "ConnsOutbound": 4611686018427388000,
  "FD": 524288,
  "Memory": 8133804032,
  "Streams": 4611686018427388000,
  "StreamsInbound": 8653,
  "StreamsOutbound": 4611686018427388000
}

Signed-off-by: Antonio Navarro Perez [email protected]

[BigLep]

Thanks @ajnavarro. I'm wondering if we should have a message where the resource manager is enabled or not. Something like:

"go-libp2p resource protection disabled"

It emphasizes the purpose (node protection) and makes it clear when someone is forgoing that protectin.

[ajnavarro]

@BigLep added a message when starting the daemon and RM is disabled.

[Jorropo]

SGTM

[lidel]

(unrelated) @ajnavarro if you have multiple "wip" commits like https://github.com/ipfs/kubo/pull/9470/commits it is perfectly fine to just squash-merge :)

(makes eyeballing https://github.com/ipfs/kubo/commits/master and inspecting release diff a bit easier for person making the release dance)