Date: Tue, 21 Jul 2015 16:53:15 +0200 From: Stefano Garzarella <stefanogarzarella@gmail.com> To: soc-status@freebsd.org Cc: Luigi Rizzo <rizzo@iet.unipi.it>, Peter Grehan <grehan@freebsd.org>, Neel Natu <neel@freebsd.org> Subject: ptnetmap on bhyve status report Message-ID: <CAO0mX5Ydv31Oz1sr1NvyYCrSyPBz3b9PicV8psn7DRENrJG0sQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Dear All, I've successfully mapped the netmap memory in the guest VM last week. I added a new IOCTL in vmm.ko to map netmap memory (returned by the mmap() in the byvhe user space application) in the guest VM. In this way the netmap memory is shared between guest and host. After that I created a kthreads in netmap-host to comunicate with the netmap-guest through shared memory. Since I haven't yet implemented the notification mechanism, I tested it with busy-wait. Both netmap-guest and netmap-host continually poll the shared memory to wait new slots. The performance (guest->host & host->guest) is very good and it is very close to the native performance (host-host experiments) and Linux-KVM performance: - physical ixgbe device [14 Mpps ~line rate] - VALE software switches [24 Mpps] - netmap-pipes (shared memory channels) [50 Mpps] I'm going to start the last step: implement notification mechanism in bhyve/FreeBSD. We want to have a mechanism to exchange notifications between guest and host kthreads. The code is available on https://svnweb.freebsd.org/socsvn/soc2015/stefano/ptnetmap/stable/10/ Thanks, Stefano Garzarella.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAO0mX5Ydv31Oz1sr1NvyYCrSyPBz3b9PicV8psn7DRENrJG0sQ>