DragonFlyBSD bugtracker: Issues
https://bugs.dragonflybsd.org/
https://bugs.dragonflybsd.org/favicon.ico?1629395208
2018-05-07T18:30:08Z
DragonFlyBSD bugtracker
Redmine
DragonFlyBSD - Bug #3133 (Closed): The documentation on adding file based swap space is incorrect
https://bugs.dragonflybsd.org/issues/3133
2018-05-07T18:30:08Z
gjs278
gjs278@yahoo.com
<p>On <a class="external" href="https://www.dragonflybsd.org/docs/handbook/Configuration/#index14h2">https://www.dragonflybsd.org/docs/handbook/Configuration/#index14h2</a></p>
<p>Step 5 is incorrect. The command</p>
<ol>
<li>vnconfig -e /dev/vn0b /usr/swap0 swap</li>
</ol>
<p>Does not seem to work because /dev/vn0b doesn't exist.</p>
<ol>
<li>vnconfig -e /dev/vn0 /usr/swap0 swap</li>
</ol>
<p>Does work. This was done on 5.2 after following the first 4 steps.</p>
DragonFlyBSD - Bug #2577 (New): virtio-blk iops performance is cpu limited on high end devices
https://bugs.dragonflybsd.org/issues/2577
2013-08-01T20:59:44Z
gjs278
gjs278@yahoo.com
<p>Qemu 1.5.2 on Gentoo AMD64 kernel 3.10.4 host with an i7 980x processor at 4.2ghz</p>
<p>qemu-system-x86_64 -machine accel=kvm -cpu host -drive file=/dev/fioa3,if=virtio,cache=none,aio=native -balloon virtio -smp 6 -m 6144M</p>
<p>/dev/fioa3 is a 160gb slc fusion-io card</p>
<p>DragonFlyBSD 3.4.2-RELEASE is the guest OS</p>
<ol>
<li>/tmp/rr1 /dev/vbd0<br />Device /dev/vbd0 bufsize 512 limit 10.800GB nprocs 32<br />randrand 1.001s 24293 loops = 41.202uS/loop<br />randrand 1.002s 24384 loops = 41.072uS/loop<br />randrand 1.001s 24633 loops = 40.640uS/loop</li>
</ol>
<ol>
<li>/tmp/rr1 /dev/vbd0 4096<br />Device /dev/vbd0 bufsize 4096 limit 10.800GB nprocs 32<br />randrand 1.001s 24333 loops = 41.119uS/loop<br />randrand 1.002s 24389 loops = 41.052uS/loop<br />randrand 1.001s 24367 loops = 41.093uS/loop</li>
</ol>
<ol>
<li>/tmp/rr1 /dev/vbd0 16384<br />Device /dev/vbd0 bufsize 16384 limit 10.800GB nprocs 32<br />randrand 1.001s 21006 loops = 41.619uS/loop<br />randrand 1.002s 21167 loops = 41.348uS/loop<br />randrand 1.001s 20520 loops = 48.850uS/loop</li>
</ol>
<p>cpu usage on the host nears 100% while /tmp/rr1 is running. at nprocs 32, the device should be capable of at least 100k iops. the same 25k limit is seen using an ssd array as well.</p>