Date: Mon, 10 Jul 2017 12:49:22 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> Cc: freebsd-current@freebsd.org, otacilio.neto@bsd.com.br Subject: Re: type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730 Message-ID: <20170710094922.GQ1935@kib.kiev.ua> In-Reply-To: <20170710184528.8677740bc55681e331c2fbea@dec.sakura.ne.jp> References: <1c37db96-7cd2-91c9-011c-967a32a97f05@bsd.com.br> <20170710154046.58c3d7b14a227a20bea3e55b@dec.sakura.ne.jp> <20170710071807.GO1935@kib.kiev.ua> <20170710184528.8677740bc55681e331c2fbea@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 10, 2017 at 06:45:28PM +0900, Tomoaki AOKI wrote: > Hm, for example, sysutils/lsof (userspace app) depends on kernel > source, and I thought the one Otacilio mentioned is something like it. lsof purpose is to dig into a kernel memory to gather information about the process state and opened files. To do this, lsof authors have to use internal kernel data structures. The library which is discussed in the thread uses public interfaces, but then tries to pack the returned data into internal kernel structure. If this is true, then the breakage is on the library side.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170710094922.GQ1935>