Date: Tue, 11 May 2021 09:04:14 -0400 From: Mark Johnston <markj@freebsd.org> To: Francois ten Krooden <ftk@nanoteq.com> Cc: Konstantin Belousov <kostikbel@gmail.com>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Vector Packet Processing (VPP) portability on FreeBSD Message-ID: <YJqAznByy772Tc82@nuc> In-Reply-To: <AB9BB4D903F59549B2E27CC033B964D6C4F8D11A@NTQ-EXC.nanoteq.co.za> References: <AB9BB4D903F59549B2E27CC033B964D6C4F8BECE@NTQ-EXC.nanoteq.co.za> <YJk%2BxyUQx5/ENPRj@kib.kiev.ua> <AB9BB4D903F59549B2E27CC033B964D6C4F8D11A@NTQ-EXC.nanoteq.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 11, 2021 at 12:43:10PM +0000, Francois ten Krooden wrote: > On Monday, 10 May 2021 16:10 Konstantin Belousov wrote: > > > > On Mon, May 10, 2021 at 11:08:18AM +0000, Francois ten Krooden wrote: > > > 3. What are suitable alternatives for reading information from procfs and > > sysfs on FreeBSD? > > Understand what information is obtained, then what for is it actually used, > > then match it against equivalent FreeBSD approach, then gather the > > required information. > > Thank you. This was basically what we suspected. > One of the ones we are unsure about is what the equivalent of /proc/self/pagemap on Linux would be. > The one idea we had is using procstat_getvmmap from libprocstat, but haven't finished investigating yet. I believe DPDK's libeal uses /proc/pagemap to look up the physical address of large page mappings. Assuming you want to do the same thing, there is the MEM_EXTRACT_PADDR /dev/mem ioctl. It was added specifically for DPDK. See the mem(4) man page for details on its usage.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YJqAznByy772Tc82>