From owner-svn-doc-all@FreeBSD.ORG Sun Jul 20 23:49:47 2014
Return-Path: The so-called "CUSE4BSD" has been imported into the base
- system of &os;-11. CUSE is short for character device in
- userspace. The CUSE library is a wrapper for the
+ The so-called The CAM Target Layer (CTL), used as base for new kernel iSCSI
+ The CAM Target Layer (CTL), used as the base for the new kernel iSCSI
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
@@ -278,7 +278,7 @@
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
+ subsystems are initialized. Also, to facilitate migration from
syscons(4) to vt(4), multiple virtual
terminal subsystems in the kernel are now supported. It is
controlled by a small module with just one kernel environment
@@ -288,8 +288,7 @@
The GENERIC kernel configuration for the amd64 and i386
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.CUSE4BSD
has been imported into the base
+ system of &os;-11. CUSE is short for character device in
+ userspace
. The CUSE library is a wrapper for the
devfs(8) kernel functionality which is exposed
through /dev/cuse. In order to function, the CUSE kernel code
must either be enabled in the kernel configuration file or
@@ -153,7 +153,7 @@
request rate increased by many times, reaching up to 600K
requests per second on modern hardware.
The project finally received a man page, so now
vt(4) is not only the project name, but also a link
@@ -350,7 +349,7 @@
vidcontrol(1).
The ports-mgmt/poudriere-devel port is aware of how - to build ports via an emulator. Configuration of the +
The ports-mgmt/poudriere-devel port is capable of + building ports via an emulator. Configuration of the miscellaneous binary image activator is required prior to a poudriere-devel run.
@@ -414,7 +413,8 @@ of builds. They can be viewed on the "Status of ports building" link. -On current or latest stable/10:
+To build packages via emulation, on current or latest + stable/10:
Clone the github repository, and switch to the bsd-user branch. Then run:
@@ -439,7 +439,7 @@Install poudriere-devel from ports. It knows how to set up things.
-Build poudriere jail to do all the magic:
+Create a poudriere jail to do all the magic:
poudriere jail -c -j 11armv632 -m svn -a armv6 \
-v head
In May and June a huge clean-up operation took place to remove the last bits and pieces targeting easy_install. In @@ -609,7 +610,7 @@ vt(4) selection to the UEFI boot path.
Snapshots are now built as dual-mode images, and should boot - via BIOS and UEFI. Our plan is to merge the UEFI and + via both BIOS and UEFI. Our plan is to merge the UEFI and vt(4) work to stable/10 to appear in &os; 10.1-RELEASE.
@@ -754,18 +755,18 @@Since the last report the following items have been - completed, which allow for a working demo of OpenStack compute - node on a &os; host using OpenContrail solution for network + completed, which allow for a working demo of an OpenStack compute + node on a &os; host using OpenContrail for network virtualization:
The annual board meeting was held in Ottawa, Canada, in May. - Directors and officers were elected, and did some long term + Directors and officers were elected, and we 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 + mapping, and our near-term goals. We also met with the core team to discuss roles and responsibilities, project roadmapping, and what we can do to help the Project more.
@@ -849,7 +850,7 @@ (southeastlinuxfest.org).Hardware was purchased to support an upgrade at Sentex. A - new high capacity 1Gbps switch was deployed to allow for more + 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.
@@ -921,17 +922,17 @@SDIO is an interface designed as an extension of the existing SD card standard, which allows the connecting of different - peripherals to the host with a standard SD controller. + peripherals to a host with a standard SD controller. Peripherals currently sold on the general market include WLAN/BT modules, cameras, fingerprint readers, and barcode scanners. Additionally, SDIO is used to connect some - peripherals in products like Chromebooks and Wandboard. A + peripherals in products like Chromebooks and Wandboards. A prototype of the driver for the Marvell SDIO WLAN/BT (Avastar 88W8787) module is also being developed, using the existing Linux driver as the reference.
-SDIO card detection and initialization already work, most - needed bus methods are implemented and tested.
+SDIO card detection and initialization already work. Most + necessary bus methods are implemented and tested.
The WiFi driver is able to load firmware onto the card and
initialize it. A rewrite of the MMC stack as a transport
@@ -942,11 +943,11 @@
The DRM generic code update is ready, but it breaks the @@ -1214,7 +1214,7 @@
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 + and Clang. The relevant ports are still not ready to hit the ports tree, unfortunately.
@@ -1291,8 +1291,8 @@ kernel test suite was done. The issues found were debugged and fixed. -Most of the problems are related to the bugs in the - interaction of vnode and node lifetime, culminating in e.g., +
Most of the problems are related to bugs in the + interaction of the vnode and node lifetime, culminating in e.g., unmount races and dotdot lookup bugs.
@@ -1319,12 +1319,12 @@Analysis of the performance of the latest 9.3 version of PostgreSQL on &os;-CURRENT has been performed. The issues - which prevented the good scalability on a 40-core machine were + which prevented good scalability on a 40-core machine were determined, and changes prototyped which solve the bottlenecks.
The URL above provides a paper which contains a detailed - explanation of the issues and solutions, together with the + explanation of the issues and solutions, together with a graph demonstrating the effects on scalability.
@@ -1376,18 +1376,18 @@ frequency of system releases but also frees much developer time to be spent on different areas of the project. -Furthermore, a new website and forum is being worked at, +
Furthermore, a new website and forum is being worked on, replacing the old-fashioned website that offers only limited functionality. The new website will be linked to the server database, providing real-time updates about the project.
-In addition, a new platform for collaborated development is +
In addition, a new platform for collaborative development is in the works. A service addon has been created for the GitLab project, which is a drop-in replacement of the popular GitHub website. The choice was made to host our own solution and not rely on GitHub itself. In retrospect this appears to be a good decision. The recent development where GitHub removed - projects after DCMA-takedowns being sent is incompatible with + projects after DCMA takedowns being sent is incompatible with the philosophy of free-flow-of-information, which the ZFSguru project is a strong proponent of. By hosting our own solution, we have avoided any dependency on third party @@ -1402,12 +1402,12 @@ web-interface. This functionality provides an easy way to upgrade the current system by performing a new clean installation, but migrate all relevant configuration to the - new installation. It also allows to 'backup' all system + new installation. It also allows to backup all system configuration in a single file to be stored on a different machine should things go awry.
A longer version of this status report giving a wider
- perspective on the project, can be found at the
+ perspective on the project can be found at the
stateoftheproject
link.