Previously the majority of the VM was under a single token, the vm_token; now vm_objects (mappable entities) are each under a private token, concurrent page faults in the same object can proceed, and VM SMP scalability overall improved. Results for Postgres and MySQL, among others, are excellent.
-Francois Tigeot [worked on benchmarks](http://leaf.dragonflybsd.org/mailarchive/kernel/2011-11/msg00004.html) comparing DragonFly 2.10 and DragonFly 2.13, among other operating systems. The [resulting graphs](http://dl.wolfpond.org/Pg-benchmarks.pdf) show how well DragonFly responds to multiple CPUs. (2.13 is the version of DragonFly that became 3.0.)
+Francois Tigeot [worked on benchmarks](http://leaf.dragonflybsd.org/mailarchive/kernel/2011-11/msg00004.html) comparing DragonFly 2.10 and DragonFly 2.13, among other operating systems. The [resulting graphs](http://dl.wolfpond.org/Pg-benchmarks.dfly_only.pdf) show how well DragonFly responds to multiple CPUs. (2.13 is the version of DragonFly that became 3.0.)
See:
* NFS server updates were pulled in from FreeBSD; read and write clustering behavior is improved.
* MSI and MSI-X support has been greatly expanded.
* Soft tokens can now be taken in shared mode in addition to the classical exclusive mode.
-* Virtual file system accounting support has been added and will serve as a basis for future file-system independent quota work
-* Appletalk support removed
+* Virtual file system accounting support has been added and will serve as a basis for future file-system independent quota work.
+* Appletalk support removed.
* dmalloc, a new memory allocator, added for x86_64 only.
+* tmpfs filesystems can now be exported via NFS.
> ### Hardware changes (non-networking)
* padlock(4) now supports the built-in random number generator and feeds entropy into the kernel's entropy pool.