Stuart Henderson @ 2019-04-15T15:39:30 +0200:
> On 2019-04-15, LÉVAI Dániel <l...@ecentrum.hu> wrote:
> > Hi!
> >
> ><TL;DR>
> > After a recent network configuration change (added re(4), vether(4)) I'm
> > experiencing this memory leak from somewhere.
> >
> > How can I check/query how much memory the kernel (or parts of it) is
> > using over time, besides running top(1) with system processes shown --
> > I'm also staring at systat(1)'s `malloc' and `pool' views but I'm not
> > really sure what I'm (or rather what I should be) looking at.
> ></TL;DR>
>
> Sorry I didn't read the whole lot, but from skimming through it's likely
> to be kernel not userland (which is why you don't see much detail in top).
> There are likely some clues in output from the following:
>
> netstat -m
> vmstat -m
> systat -b mbuf
No worries, this is perfect, thank you for the tips.
I'm already wondering about the `mbufs' output from systat(1)
(especially the ALIVE column):
After a reboot + 20 minutes:
1 users Load 0.46 0.38 0.33 firefly.ecentrum.hu 16:40:43
IFACE LIVELOCKS SIZE ALIVE LWM HWM CWM
System 0 256 4100 260
2048 3717 468
2112 53 7
4096 128 20
9216 17 12
After two days:
1 users Load 0.14 0.20 0.22 firefly.ecentrum.hu 15:00:00
IFACE LIVELOCKS SIZE ALIVE LWM HWM CWM
System 0 256 215K 13780
2048 * 26954
2112 66 9
4096 128 25
9216 11 11
How does ALIVE: 215k look after two days uptime with mild internet
traffic? Is this something that could be a potential culprit or am I
just reading things into that?
And I'm just guessing but that star either means infinite :) or that it
couldn't even write the number into that space.
Dani
--
LÉVAI Dániel
PGP key ID = 0x83B63A8F
Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
