Date: Wed, 15 May 2019 01:38:47 +0300 From: Konstantin Belousov <kib@freebsd.org> To: Thomas Munro <tmunro@freebsd.org> Cc: Bob Bishop <rb@gid.co.uk>, Andriy Gapon <avg@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>, Alan Somers <asomers@freebsd.org> Subject: Re: leaked swap? Message-ID: <20190514223847.GK2748@kib.kiev.ua> In-Reply-To: <CA%2BhUKGKFrJvRgzy_rWfS%2BWpFZahV0RheSgakjYvvb-33aW%2BT=Q@mail.gmail.com> References: <9c5eaa94-f55b-464a-ab0f-267e7fce4bd0@FreeBSD.org> <20190318153230.GS96870@kib.kiev.ua> <782c2d4b-6920-085b-5489-65fae462a194@FreeBSD.org> <C48F6C8D-28AB-4B46-A7A6-516321C2303B@gid.co.uk> <CA%2BhUKGKFrJvRgzy_rWfS%2BWpFZahV0RheSgakjYvvb-33aW%2BT=Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 15, 2019 at 10:02:51AM +1200, Thomas Munro wrote: > 1. As mentioned, you can't list 'em (unlike Linux, where you can just > ls /dev/shm). There's a TODO note, but it's not clear whether it's > best to extend ipcs or create a new userspace tool, and it wasn't > immediately clear to me how to feed the arbitrary sized results back > to userspace. I had a scheme worked out where you'd keep calling a > sysctl repeatedly to collect the data until it was done, and it'd > sometimes tell you you need a bigger buffer (because you probably have > to drain at least a whole hash table bucket at a time), but an > experienced FreeBSD hacker told me that was BS, and maybe what's > needed is a device you read. As well as the list-all-the-segments > tool, you'd also want to be able to unlink to tidy up. https://reviews.freebsd.org/D20258
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190514223847.GK2748>