From owner-p4-projects@FreeBSD.ORG Sun Apr 25 19:35:20 2010
Return-Path: SUMMARY GOES HERE This report covers &os; related projects between January and
+ March 2010. Being the first of the four reports planned for 2010 with
+ 46 entries, it shows a good progress of the &os; Project and proves
+ that our committers are keeping up with the latest trends in the OS
+ development. During this period, a new minor version of &os;,
+ 7.3-RELEASE, has been released, while the release process for
+ 8.1-RELEASE is soon to begin and is planned to be released later this
+ summer. Thanks to all the reporters for their excellent work! We hope you
+ enjoy the reading. Thanks to all the reporters for the excellent work! We hope you
- enjoy reading. Please note that the deadline for submissions covering the
+ period between April and June 2010 is July 15th, 2010. The ALQ(9) implementation and KPI has been rototilled and modified
(one more patch needs to be committed) to support variable length
- messages. In addition, it can now be compiled and loaded as a kernel
+ messages. In addition, it can now be compiled and loaded as a kernel
module. With the ALQ changes in head, SIFTR can finally be imported.
In February work was done to address resources leaks in the +
In February work was done to address resource leaks in the (virtual) network stack, especially on teardown.
During that time also multiple general run-time problems and leaks
@@ -193,11 +203,11 @@
especially radix/routing table memory.
In addition epair(4) was enhanced and debugging was improved.
Work on this had been sponsored by ISPsystem.
+This work was sponsored by ISPsystem.
mfsBSD is a set of scripts that generates a bootable image (e.g. a +
mfsBSD is a set of scripts that generate a bootable image (e.g. an ISO file) that creates a working minimal installation of &os; that is completely loaded into memory (mfs).
@@ -320,7 +330,7 @@We grew our board of directors by adding Erwin Lansing. This will expand our representation in Europe. Erwin brings ports knowledge and - expertise the the board.
+ expertise to the board.We continued our work on infrastructure projects to beef up hardware for package-building, network-testing, etc.
@@ -389,9 +399,9 @@'tbemd' stands for Target Big Endian Must Die. The current build systems requires that one define TARGET_BIG_ENDIAN for either big endian MIPS or big endian ARM processors. There are many problems - with this approach. The resulting system will nott create the proper - binaries without TARGET_BIG_ENDIAN defined. There is no way to know - what the endian is of the system you are running easily. There are + with this approach. The resulting system will not create the proper + binaries without TARGET_BIG_ENDIAN defined. There is no easy way to + know what the endian is of the system you are running. There are many issues with ports, since they do not use bsd make, so do not pick up the extra flags that are added if TARGET_BIG_ENDIAN is defined.
@@ -403,13 +413,13 @@ mips big endian and 64-bit mips little endian respectively. ARM will move to arm (little endian) and armeb (big endian), again following the standards set elsewhere. To facilitate a number of different - MACHINE_ARCHs all built form the same source, a new MACHINE_CPUARCH + MACHINE_ARCHs all built from the same source, a new MACHINE_CPUARCH is introduced and represents the sources needed to build CPU support for a given MACHINE_ARCH.In addition, MACHINE_ARCH is overused in the build system today.
Many of its uses are gratuitous and can be simplified. Many of its
- uses d not scale well and need to be refactored into a system that
+ uses do not scale well and need to be refactored into a system that
will scale well. A per MACHINE/MACHINE_ARCH/MACHINE_CPUARCH selection
mechanism for makefile snippets will be introduced to move much of
the current if spaghetti into more controlled lists.
@@ -445,9 +455,9 @@
Work is underway to allow the &os; build system to use out of tree - compilers and binary utitilies (loaders, linkers, etc), especially in + compilers and binary utililies (loaders, linkers, etc), especially in a cross compilation environment. While it is possible to swap out the - compiler with relative ease with a compatible compiler, swapping out + compiler with a compatible compiler relatively easily, swapping out the toolchain is more involved. In addition, when using an external compiler to build the system, certain parts of buildworld can be omitted.
@@ -623,8 +633,8 @@ -The purpose of this project is to provide embedded &os; with - generic and flexible scheme supporting NAND Flash devices. The +
The purpose of this project is to provide embedded &os; with a + generic and flexible scheme to support NAND Flash devices. The framework provides a set of KOBJ interfaces inside the kernel, which allow for uniform and flexible management of the NAND devices:
@@ -638,25 +648,25 @@ erase, get status etc.)Part of the infrastructure is a full system simulator of - ONFI-compliant devices (NANDsim), with userland control application. - This allows for exercising the framework on platforms without real + ONFI-compliant devices (NANDsim), with a userland control application. + This allows for exercising of the framework on platforms without real NAND chips.
Current state highlights:
The main focus on this work is, at the moment, to identify general +
The current focus is to identify general architectural problems and dependencies we do have between these two address families as well as with the upper layer protocols. This will - allow us to discuss those problems at one point, seek solutions but - also to keep in mind that we do not only need to take care of being - able to compile out INET6 in the future.
+ at some point allow us to discuss the issues and seek solutions, + preparing for a future where we can remove either INET or INET6 from + the system.Once we will have a stable, in-tree way to compile out either - address family, optimizations wrt. to size, as well as user space + address family, optimizations wrt. size, as well as user space will need to be worked on. In addition to this, the work is believed - to help should we further head into the direction of network stack + to help should we further head in the direction of network stack modularization.
@@ -857,7 +867,7 @@Although the bare bones of the NFS Version 4 support was released - in &os;8.0, the integration has been progressing slowly and support - should be functional for &os;8.1 for RFC3530 (NFS Version 4.0).
+ in &os; 8.0, the integration has been progressing slowly and support + should be functional for &os; 8.1 for RFC3530 (NFS Version 4.0). -Post &os;8.1, I believe the focus will be on code cleanup and, - under a projects area of svn, some experimental work on agressive +
Post &os; 8.1, I believe the focus will be on code cleanup and, + under a projects area of svn, some experimental work on aggressive whole file caching to client disk.
@@ -916,21 +926,22 @@Based on the idea of Jeff Roberton, we reimplemented the path for +
Based on the idea of Jeff Roberson, we reimplemented the path for read(2)/write(2) syscalls using page cache (in wide sense) to - eliminate the issues with recursive vnode and buffers locks + eliminate the issues with recursive vnode and buffer lock acquisitions. The usual reads and writes are no longer calls into - VOP_READ/VOP_WRITE, the operation is done by copying user buffers to - or from the pages of vnode. This fixes known deadlocks when reads or - writes are done over file-mmaped buffers.
+ VOP_READ/VOP_WRITE; the operation is done by copying user buffers to + or from the pages of the vnode. This fixes known deadlocks when reads + or writes are done over file-mmaped buffers. -The patch changes the performance characteristics of I/O, we +
The patch changes the performance characteristics of I/O, and we observed both better and worse behaviour. If filesystem implements VOP_GETPAGES and VOP_PUTPAGES without referencing buffer cache, buffers are completely eliminated from the i/o path (not true for UFS @@ -965,7 +976,7 @@
The alpha version of libunwind library port for &os; x86 and x86_64 is completed and imported into the official libunwind git repository. Libunwind is the library to perform dynamic unwinding of - the stacks, using dwarf call frame information. Library features + stacks, using dwarf call frame information. The library features remote unwinding using ptrace(2), very fast setjmp(3) implementation and more interesting features.
@@ -1037,7 +1048,7 @@We have recently completed a massive revision of ipfw and - dummynet, and the result have been committed to HEAD and stable/8. + dummynet, and the result has been committed to HEAD and stable/8. The main features introduced with this work are:
Johann was busy keeping the german website in sync with updates to +
Johann was busy keeping the German website in sync with updates to FreeBSD.org. However, there are still parts of the website that remain untranslated. We are looking for more support in maintaining - the german website.
+ the German website. -&os; users with german language skills are always welcome to join +
&os; users with German language skills are always welcome to join our efforts in translating the documentation and/or fixing bugs.
QAT has been running on a single server for about two years now and has proven very effective at catching problems with ports commits. Many of the problems it cannot catch are architecture or - branch related. By moving QAT to a vmware box capable of running + branch related. By moving QAT to a VMware box capable of running arbitrary versions of &os; on both amd64 and i386 this limitation will be removed.
@@ -1619,7 +1630,7 @@ fixed.It is now possible for interested parties to be emailed a weekly, - customized, report along the lines of the the above. If you are + customized, report along the lines of the above. If you are interested in setting one up, contact linimon@FreeBSD.org.
@@ -1637,7 +1648,7 @@ welcome to join us in #freebsd-bugbusters on EFnet. We are always looking for additional help, whether your interests lie in triaging incoming PRs, generating patches to resolve existing problems, or - simply helping with the database housekeeping (identifying dulicate + simply helping with the database housekeeping (identifying duplicate PRs, ones that have already been resolved, etc). This is a great way of getting more involved with &os;! @@ -1782,9 +1793,9 @@ well as some changes to OpenSSH as well as plugins for PAM, NSS and can support. -We have used several existing work and updated them to use new +
We have used several existing works and updated them to use new OpenLDAP API, fixed several bugs and integrated them together. All - these work are under BSD or similar license and our new work would be + these works are under BSD or similar license and our new work would be under 2-clause BSD license. Currently, we support storing user identity, password and SSH public keys in LDAP tree.