Date: Thu, 9 Jan 2020 13:25:55 +0100 From: Gary Jennejohn <gljennjohn@gmail.com> To: Hans Petter Selasky <hps@selasky.org> Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, current@freebsd.org, Jeff Roberson <jeff@freebsd.org>, Konstantin Belousov <kib@FreeBSD.org> Subject: Re: M_TEMP trouble in 13.0-CURRENT #0 r355131M Message-ID: <20200109132555.59c2c14e@ernst.home> In-Reply-To: <100f4e72-ef8b-07dc-b1e1-2a3ef4853d31@selasky.org> References: <4164.1578563950@critter.freebsd.dk> <4e52b23e-32ed-6556-a74e-22c809a17fe0@selasky.org> <f0c4c466-c20f-8824-0138-6b5d45004256@selasky.org> <100f4e72-ef8b-07dc-b1e1-2a3ef4853d31@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 9 Jan 2020 12:58:28 +0100 Hans Petter Selasky <hps@selasky.org> wrote: > Hi Jeff and Konstantin, > > You have a logical breakage after the domainset patches for malloc. The size used for allocation statistics is not the same like for freeing causing messed up "vmstat -m". > > Also you should audit the code for zero-sized allocations, because upon alloc, zero-sized is not counted, while on free it is. > > See attached patch. > Yeah, the patch produces much saner output. -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200109132555.59c2c14e>