From owner-freebsd-current@freebsd.org  Mon Jul 10 09:49:33 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EF98DA2875
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 10 Jul 2017 09:49:33 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 04ACC82DA3
 for <freebsd-current@freebsd.org>; Mon, 10 Jul 2017 09:49:32 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from tom.home (kib@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v6A9nM8C060106
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Mon, 10 Jul 2017 12:49:23 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v6A9nM8C060106
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id v6A9nMAq060105;
 Mon, 10 Jul 2017 12:49:22 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
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>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170710184528.8677740bc55681e331c2fbea@dec.sakura.ne.jp>
User-Agent: Mutt/1.8.3 (2017-05-23)
X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no
 autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jul 2017 09:49:33 -0000

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.