From owner-svn-doc-all@FreeBSD.ORG Tue Jul 15 12:19:30 2014
Return-Path: The &os; RPC stack, used as base for its NFS server, took
- multiple optimizations to improve its performance and SMP
- scalability. Algorithmic optimizations allowed to reduce
+ The &os; RPC stack, used as a base for its NFS server, received
+ multiple optimizations to improve performance and SMP
+ scalability. Algorithmic optimizations reduced
processing overhead, while improved locking allowed it to
scale up to at least 40 processor cores without significant
lock congestion. Combined with some other kernel
- optimizations that allowed to increase peak NFS request rate
+ optimizations, the peak NFS request rate increased
by many times, reaching up to 600K requests per second on
modern hardware. The CAM Target Layer (CTL), used as base for new kernel iSCSI
- server, also took series of locking optimization, that allowed
- to increase its peak request rate from ~200K to ~600K IOPS
- with potential of reaching reate of 1M request per second.
+ server, also received a series of locking optimizations which allowed
+ its peak request rate to increase from ~200K to ~600K IOPS
+ with the potential of reaching a rate of 1M requests per second.
That rate is sufficient to completely saturage 2x10Gbit
Ethernet links with 4KB requests. For comparison, the port of
net/istgt (user-level iSCSI server) on the same hardware with
- equal configuration shown only 100K IOPS.
There is also ongoing work on improving CTL functionality. - It was already made to support 3 of 4 VMWare VAAI storage + It was already made to support three of four VMWare VAAI storage acceleration primitives (net/istgt supports 2), while the goal is to reach full VAAI support during next months.
-With all above, and earlier improvements in CAM, GEOM, ZFS - and number of other kernel areas coming soon FreeBSD 10.1 may +
With all these improvements, and earlier improvements in CAM, GEOM, ZFS, + and a number of other kernel areas coming soon, FreeBSD 10.1 may become the fastest storage release ever. ;)
These projects are sponsored by iXsystems, Inc.
@@ -203,15 +203,15 @@Booting &os; on the ARM Foundation Model has made a lot of progress since the last status report. An initial pmap - implementation has been written. With this &os; is able to + implementation has been written. With this, &os; is able to enter the Machine Independent boot code. The required autoconf functions have been added allowing &os; to start scheduling tasks. Finally the cpu_switch and copystr - functions were added. With these two &os; will boot to the + functions were added. With these two, &os; will boot to the mountroot prompt.
Work has started on supporting exceptions, including - interrupts. This will start to allow more developers to start + interrupts. This will allow more developers to start working on device drivers.
@@ -273,24 +273,24 @@ integration with graphics modes and broader character set support. -Since last report - vt(4) got ability to make early driver selection. - vt(4) select best successfully probed driver before - most of kernel subsystems. Also, to make easy migration from +
Since the last report, + vt(4) gained the ability to make early driver selection. + vt(4) selects the best successfully-probed driver before + most other kernel subsystems. Also, to make easy migration from syscons(4) to vt(4), multiple virtual - terminal subsystems in the kernel are now supported and it is + terminal subsystems in the kernel are now supported. It is controlled by a small module with just one kernel environment - variable kern.vty=sc or + variable. Users can select the virtual terminal system to use by setting kern.vty=sc or kern.vty=vt.
The GENERIC kernel configuration for the amd64 and i386 - platforms include both syscons(4) and vt(4) + platforms now includes both syscons(4) and vt(4) by default. This configuration is also planned to be in the next 10-STABLE release and &os; 10.1-RELEASE.
-Project finally get his man page, so now vt(4) not - only project name, but also link to its documentation. Great +
The project finally received a man page, so now vt(4) is not + only the project name, but also a link to its documentation. Great thanks to &a.wblock; for that.
Major highlights:
@@ -361,7 +361,7 @@The ports-mgmt/poudriere-devel port is aware of how to build +
The ports-mgmt/poudriere-devel port is aware of how to build ports via an emulator. Configuration of the miscellaneous binary image activator is required prior to a poudriere-devel run.
ARMV6, MIPS32 and MIPS64 packages can be produced via full emulation. There are several packages that block a full run - of builds. They can be viewed on the Status of ports building + of builds. They can be viewed on the "Status of ports building" link.
On current or latest stable/10:
@@ -431,7 +431,7 @@gmake; gmake install
-Then setup the binmiscctl tools to do some evil hackery to +
Then set up the binmiscctl tools to do some evil hackery to redirect execution of armv6 binaries to qemu:
binmiscctl add armv6 --interpreter \ @@ -448,12 +448,12 @@
poudriere jail -c -j 11armv632 -m svn -a armv6 \
-v head
You can now run poudriere against that jail to build all the +
Now run poudriere against that jail to build all the ports:
poudriere bulk -j 11armv632 -a
-Nullfs mount your ports tree into the jail:
+Nullfs mount the ports tree into the jail:
mkdir /usr/local/poudriere/jails/11armv632/usr/ports
mount -t nullfs /usr/ports /usr/local/poudriere/jails/11armv632/usr/ports
In May, a new release policy was published as well as being +
In May, a new release policy was published and presented at the BSDCan developer conference by John Baldwin. The idea is that each major release branch (for example, 10.X) is guaranteed to be supported for at least five years, but @@ -751,14 +751,13 @@ a datacenter.
OpenContrail is a network virtualization (SDN) solution - comprising network controller, virtual router and analytics + comprising network controller, virtual router, and analytics engine, which can be integrated with cloud orchestration systems like OpenStack or CloudStack.
-This work goal is to enable &os; as a fully supported +
This work's goal is to enable &os; as a fully supported compute host for OpenStack using OpenContrail virtualized - networking. The main areas of development are the - following:
+ networking. The main areas of development are:A demo was presented at &os; DevSummit during the BSDCan2014 +
A demo was presented at the DevSummit during BSDCan2014 in Ottawa. Also, a meetup regarding the subject was organized in Krakow, Poland.
@@ -821,7 +820,7 @@We published our third issue of the &os; Journal. We have over 2700 subscriptions so far. We continued working on the - digital edition, that will allow subscribers to read the + digital edition, which will allow subscribers to read the magazine in different web browsers, including those than run on &os;. This will be available for the July/August issue of the Journal.
@@ -830,8 +829,8 @@ marketing director, to help us promote the Foundation and Project. -We held our annual board meeting in Ottawa, Canada, in May. - We elected directors and officers, and did some long term +
The annual board meeting was held in Ottawa, Canada, in May. + Directors and officers were elected, and did some long term planning. We worked on our vision, core values, project road mapping, and our near term goals. We also met with the core team to discuss roles and responsibilities, project @@ -856,8 +855,8 @@ (texaslinuxfest.org), and SouthEast LinuxFest, June 20-22 (southeastlinuxfest.org).
-We purchased hardware to support an upgrade at Sentex. A new, - high capacity, 1Gbps switch, was deployed to allow for more +
Hardware was purchased to support an upgrade at Sentex. A new + high capacity 1Gbps switch was deployed to allow for more systems to be added to the test lab. The main file server and development box was upgraded to allow more users in the lab simultaneously.
@@ -881,7 +880,7 @@ the head/ and stable/ branches, with feedback and help from Ed Maste, Glen finished work to produce release images that will, by default, provide debugging files for userland and kernel - available on the &os; Project FTP mirrors. Note, the + available on the &os; Project FTP mirrors. Note that the debugging files will not be included on the bootonly.iso, disc1.iso, or dvd1.iso images due to the size of the resulting images. @@ -892,7 +891,7 @@ changes to address these issues are in progress.Some previously completed Foundation-sponsored projects - received some enhancements or additional work. The ARM + received enhancements or additional work. The ARM superpages project was completed last year, but is now enabled by default in &os;-CURRENT. Many stability fixes and enhancements have been committed to the in-kernel iSCSI stack. @@ -930,11 +929,11 @@
SDIO is an interface designed as an extension of the existing - SD card standard, to allow connecting different peripherals to + SD card standard, which allows connecting different peripherals to the host with the standard SD controller. Peripherals currently sold at the general market include WLAN/BT modules, cameras, fingerprint readers, and barcode scanners. - Additionally SDIO is used to connect some peripherals in + Additionally, SDIO is used to connect some peripherals in products like Chromebooks and Wandboard. A prototype of the driver for the Marvell SDIO WLAN/BT (Avastar 88W8787) module is also being developed, using the existing Linux driver as @@ -943,16 +942,16 @@
SDIO card detection and initialization already work, most needed bus methods are implemented and tested.
-WiFi driver is able to load a firmware onto the card and +
The WiFi driver is able to load firmware onto the card and initialize it. A rewrite of the MMC stack as a transport - layer for CAM framework is in progress. This will allow + layer for the CAM framework is in progress. This will allow utilization of the well-tested CAM locking model and debug features.
The &os; Release Engineering Team is responsible for setting and publishing release schedules for official project releases - of &os;, announcing code freezes and maintaining the + of &os;, and announcing code freezes and maintaining the respective branches, among other things.
In early May, the &os; 9.3-RELEASE cycle entered the @@ -997,8 +996,8 @@ release cycle, and at the time of this writing, 9.3-RELEASE should be available on schedule.
-There is ongoing work to integrate support for embedded - architectures as part of the release build process. At this +
Work is ongoing to integrate support for embedded + architectures into the release build process. At this time, support exists for a number of ARM kernels, in particular the Raspberry Pi, BeagleBone, and WandBoard.
@@ -1041,7 +1040,7 @@Fiasco.OC belongs to the L4 microkernel family. A microkernel provides a bare minimum of services to the applications running on top of it, unlike traditional kernels that - incorporate a complex code like IP stacks and device drivers. + incorporate complex code like IP stacks and device drivers. This allows a dramatic decrease in the amount of code running in the privileged mode of the CPU, achieving higher security while still providing an acceptable level of @@ -1052,13 +1051,13 @@ operating system. The OS kernel runs in user-mode side-by-side with other microkernel applications such as real-time components. Multiple OSes, each with their userland - applications, may be even run in parallel, thus allowing to - build the products where processing of corporate data is + applications, can even be run in parallel, thus allowing + construction of products where processing of corporate data is strictly separated from the processing of private data.
-The project aims to create a port of &os; to Fiasco.OC - microkernel, which is a high performance L4 microkernel - developed by TU Dresden. The existing ports of OpenBSD and +
The project aims to create a port of &os; to the Fiasco.OC + microkernel, a high performance L4 microkernel + developed by TU Dresden. Existing ports of OpenBSD and Linux are used as a reference. This will allow the use of unique &os; features like ZFS in L4-based projects.
@@ -1067,7 +1066,7 @@Beyond the next release we have work in progress on allowing +
Beyond the next release, we have work in progress on allowing ranges of versions in dependency rules and handling a selection of "foreign" package repositories, such as CPAN or CTAN or PyPi.
-There are plans to use pkg(8) to package up the base system - which amongst other benefits will allow writing a universal - installer -- so you can download one installer image and from - there you can install any available version of &os; including +
There are plans to use pkg(8) to package up the base system. + Along with other benefits, this will allow writing a universal + installer: download one installer image and from + there install any available version of &os;, including snapshots.
We are also intending to use pkg(8) within the ports tree at @@ -1223,9 +1222,9 @@
Thanks to a contribution from Jan Kokemüller, Radeon 32bit ioctls are now working on 64bit hosts. This was tested successfully with Wine and StarCraft II on &os; 9.x and 11. - This required modifications to emulators/i386-wine-devel so + This required modifications to emulators/i386-wine-devel so that it works with WITH_NEW_XORG, and the creation of a new - port, libtxc_dxtn, to support texture compression required by + port, libtxc_dxtn, to support texture compression required by StarCraft II. We haven't yet had the time to polish everything, so this still requires manual steps.
@@ -1233,10 +1232,10 @@ current i915 driver. Therefore, the i915 driver must be updated before anything is committed. -Compared to last status report, OpenCL test programs are +
Compared to the previous status report, OpenCL test programs are running fine now, thanks to upgrades and fixes to libc++ and Clang. Relevant ports are still not ready to hit the ports - tree unfortunately.
+ tree, unfortunately.