From owner-svn-doc-head@FreeBSD.ORG Sat Oct 19 16:52:39 2013
Return-Path: An enhancement to the AES-NI implementation for OpenCrypto has
- been committed that significantly improves AES-XTS and AES-CBC
- decryption performance. This gives geli(8) around a
- three times performance boost on gnop(8) using AES-XTS
- compared to the old code. An enhancement to the AES-NI implementation for OpenCrypto, the
+ kernel's cryptography framework, has been committed that
+ significantly improves AES-XTS and AES-CBC decryption
+ performance. This gives geli(8) around a three times
+ performance boost on gnop(8) using AES-XTS compared to
+ the old code. These improvements are available to users of the OpenCrypto
framework and crypto(4).
To overcome this scaling limitation, a new fine-grained CAM + locking design was implemented. It implies splitting the big + per-SIM locks into several smaller ones: per-LUN locks, per-bus + locks, queue locks, etc. After these changes, the remaining + per-SIM lock protects only the controller driver internals, + reducing lock congestion down to an acceptable level and keeping + compatibility with existing drivers.
Together, the GEOM and CAM changes double the peak I/O rate, reaching up to 1,000,000 IOPS on contemporary hardware.
@@ -280,9 +283,11 @@ -The VirtIO network driver, vtnet(4), recently gained - support for multiple queues, along with a significant cleanup - and support for a few additional features.
+The VirtIO network driver, vtnet(4), is used by &os; + systems running on hypervisors including bhyve(4) and + Linux's KVM. It recently gained support for multiple queues, + along with a significant cleanup and support for a few + additional features.
@@ -460,7 +465,7 @@ completed (see links). Specifically:Capsicum is the &os; sandboxing subsystem, which presents + programmers with a capability module allowing fine-grained + delegation of rights to less-privileged processes. Casper is a + friendly daemon that provides services to sandboxed processes, + allowing policy-based access to privileged services such as DNS + resolution.
+The work on Capsicum and related projects (such as Casper, libnv, etc.) is progressing nicely. An overhaul of the cap_rights_t was committed to &os; head and @@ -1299,7 +1311,8 @@ been made to the www/webkit-gtk3 port, however it still is rather fragile.
-MATE is about ready to go in.
+MATE, a desktop environment forked from the now-unmaintained + codebase of GNOME 2, is about ready to go in.
GNOME 2 will be removed at some point in the near future. How or when this will happen is not yet clear.
@@ -1341,16 +1354,16 @@The &os; Documentation Project Primer had not changed at the same rate as the documents themselves. Some sections were - outdated and others were wordy and confusing, while information on - new changes to the documentation were not described at all. In - July, Warren gave the entire FDP Primer a fairly intense edit - for simplicity and clarity. Chapters and sections were moved - into a more logical order, and information was updated to be a - better guide to the current state. Markup examples were added - and revised. Style guidelines were also extended and updated. - The Primer is now far more consistent and usable. As always, - there is still room for improvement, and additions or - corrections are encouraged.
+ outdated and others were verbose and confusing, while + information on new changes to the documentation were not + described at all. In July, Warren gave the entire FDP Primer a + fairly intense edit for simplicity and clarity. Chapters and + sections were moved into a more logical order, and information + was updated to be a better guide to the current state. Markup + examples were added and revised. Style guidelines were also + extended and updated. The Primer is now far more consistent and + usable. As always, there is still room for improvement, and + additions or corrections are encouraged.There are some things going on with the &os;/sparc64 port - behind the scenes.
+There are several things going on with the &os;/sparc64 + port.
-For one, after having fixed all remaining problems and starting - with 9.2-RELEASE, release bits for this architecture are - cross-built on the &os; Project cluster. As one might already - have noticed, this means that from now on, sparc64 install sets - and images including those for ALPHA, BETA, and RC builds, are - already available alongside those for the other platforms - supported by &os;. It also means that since August 2013, - automatically cross-built monthly &os;/sparc64 snapshots are - distributed via the official project mirrors. Hopefully, this - can soon be extended further with freebsd-update(8) - support for sparc64.
- -Second, the X.Org ports have been fixed to work on sparc64 when - built with the WITH_NEW_XORG knob. However, it still - needs to be evaluated whether the recently committed update to - Mesa 9.1.6 has introduced any breakage.
+After having fixed all remaining problems and starting with + 9.2-RELEASE, releases for this architecture are cross-built on + the &os; Project cluster. As one might already have noticed, + this means that from now on, sparc64 install sets and images + including those for ALPHA, BETA, and RC builds, are available + alongside those for the other platforms supported by &os;. + Since August 2013, automatically cross-built monthly + &os;/sparc64 snapshots are distributed via the official project + mirrors. Hopefully, this can soon be extended further with + freebsd-update(8) support for sparc64.
+ +The X.Org ports have been fixed to work on sparc64 when built + with the WITH_NEW_XORG knob. However, it still needs + to be evaluated whether the recently committed update to Mesa + 9.1.6 has introduced any breakage.
@@ -1425,9 +1437,11 @@ manipulating the infrastructure to modernize and update it, in preperation for pkg(8) replacing the old pkg_add(1) infrastructure, as well as preparing for - &os; with Clang as default compiler. + &os; 10.0 with Clang as default compiler, libc++ + as the default C++ standard library, and iconv(1) + integrated into libc. -Automated procedures for Quality Assurance have been +
Automated procedures for quality assurance have been implemented, notably pkg-fallout. All porters are encouraged to subscribe to the associated mailing list (see links), and do their part to fix ports for pkg(8) and