Date: Mon, 1 Feb 2016 06:01:14 +0000 (UTC) From: Benjamin Kaduk <bjk@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48137 - head/en_US.ISO8859-1/htdocs/news/status Message-ID: <201602010601.u1161EeX057424@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: bjk Date: Mon Feb 1 06:01:13 2016 New Revision: 48137 URL: https://svnweb.freebsd.org/changeset/doc/48137 Log: First half of an editing pass on the 2015Q4 report wblock has already done the heavy lifting, so this diff is not quite so big. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Mon Feb 1 04:48:36 2016 (r48136) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml Mon Feb 1 06:01:13 2016 (r48137) @@ -674,13 +674,13 @@ For example, 9% of 75% of MAXVNODES is more than 566000 vnodes to reclaim whenever <tt>vnlru_proc()</tt> becomes active.</p> - <p>The <tt>vfs.vlru_alloc_cache_src</tt> sysctl is removed. New + <p>The <tt>vfs.vlru_alloc_cache_src</tt> sysctl is removed. The new code frees namecache sources as the last chance to satisfy the highest watermark, instead of selecting source vnodes randomly. This provides good enough behavior to keep <tt>vn_fullpath()</tt> working in most situations. Filesystem layouts with deep trees, where the removed knob was required, - is thus handled automatically.</p> + are thus handled automatically.</p> <p>As the kernel allocates and frees vnodes, it fully initializes them on every allocation and fully releases them @@ -733,7 +733,7 @@ from ancient 1Gbps 22xx to modern 16Gbps 26xx.</li> <li>Port database handling was unified for target and - initiator roles, allowing HBA port to play both roles at the + initiator roles, allowing an HBA port to play both roles at the same time.</li> <li>The maximal number of ports was increased from 256 to @@ -1202,7 +1202,7 @@ <p>Instead of trying to deduce the deadlock from looking at the current VM state, the new OOM handler tracks the history of - page daemon passes. Only when several consequtive passes + page daemon passes. Only when several consecutive passes failed to meet the paging target is an OOM kill considered necessary. The count of consequent failed passes was selected empirically, by testing on small (32M) and large (512G) @@ -1213,7 +1213,7 @@ <p>Another issue was identified with the algorithm which selects a victim process for OOM kill. It compared the counts of pages mapping entries (PTEs) installed into the machine paging - structures. For different reasons, machine-dependent VM code + structures. For different reasons, the machine-dependent VM code (pmap) may remove the pte for a memory-resident page. Under some circumstances related to other measures to prevent low memory deadlock, very large processes which consume all system @@ -1339,7 +1339,7 @@ complete list of changes is documented in the <a href="https://github.com/openbsm/openbsm/blob/master/NEWS">NEWS</a>; file on GitHub. The release was imported into &os; HEAD and - merged to &os; 10-STABLE. As such it will be part of &os; + merged to &os; 10-STABLE. As such, it will be part of &os; 10.3-RELEASE.</p> </body> @@ -1762,9 +1762,9 @@ <p>The bugmeister team has gained a new member, Mahdi Mokhtari (mokhi64@gmail.com). Mahdi has been contributing to the &os; Project for just over one month. After getting started by - creating ports for Chef-Server and MySQL 5.7 (With Bernard + creating ports for Chef-Server and MySQL 5.7 (with Bernard Spil's help), an introduction to &a.koobs; led to guidance on - appropriate projects, such as Bugzilla development, helping + appropriate projects, such as Bugzilla development to help Bugmeister, the Bugzilla Triage team, Developers, and the community by making issue tracking better. This is how things are going so far:</p> @@ -1781,7 +1781,7 @@ <ul> <li>We have made improvements to the AutoAssigner module - (not yet deployed) that was previously developed by Marcus + (not yet deployed) that was previously developed by &a.mva; to assign port bugs to their maintainers by default, such as: @@ -1924,8 +1924,8 @@ Of note, the release build code no longer produces MD5 checksums, in favor of SHA512.</p> - <p>Toward the end of the year, much of the primary focus was - centered around the upcoming &os; 10.3 release cycle, + <p>Toward the end of the year, focus was primarily + centered on the upcoming &os; 10.3 release cycle, which will begin in January 2016.</p> <p>As always, help testing development snapshot builds is @@ -2081,7 +2081,7 @@ files.</p> <p>A patch has been uploaded to Phabricator for review. The - project is currently being updated to address the review + patch is currently being updated to address the review comments, and should be committed as soon as it is accepted. For more technical details, please visit the FreeBSD-security mailing list archive or see the Phabricator review.</p> @@ -2167,22 +2167,22 @@ newcomers to issue tracking. It naturally resulted in a entire review of the tracking process from its very elementary aspects. This "fresh eyes" - participation spotted minor details along the process, + participation spotted minor details during the process, giving the opportunity to scrutinize actual procedures on a number of smaller points, followed by proposals on how to improve the overall Issue Tracking and Management. The new ideas include both organizational and technical ideas and solutions, such as new or modified keywords or flags for better classification, the triage workflow, and Bugzilla - technical improvements among others.</li> + technical improvements, among others.</li> <li>An important goal is producing documentation about best practices for using Bugzilla and issue management workflow. This documentation should be aimed not only at people directly engaged in issue triage tasks, but also at general - users. Another relevant point is that feedback from triage + users. Another relevant point is that feedback from the triage team can be used to improve Bugzilla in terms of adjusting - existing features to best fit &os;'s needs, and development + existing features to best fit &os;'s needs, and the development of new features (please see Mahdi "Magic" Mokhtari's report on "Bugzilla improvements").</li> @@ -2195,13 +2195,13 @@ linked in this report.</li> </ul> <p>Since the Issue Triage Team is very young, we expect more - information be available and more actions be reported in the - next Status report.</p> + information be available and more actions to be reported in the + next status report.</p> </body> <help> <task> - <p>Set up the Wiki namespace and organize the brainstorm + <p>Set up the Wiki namespace and organize the brainstorming document into a meaningful set of documents.</p> </task> @@ -2379,7 +2379,7 @@ <li>Sent out patches to add an interrupt counter for Hyper-V VMBus interrupts (so the user can easily get - the statistical information about VMBus interrupts), + statistical information about VMBus interrupts), and fix the KVP daemon's poll timeout (so the daemon will avoid unnecessary polling every 100 milliseconds.</li> @@ -2454,7 +2454,7 @@ capabilities of Mellanox's 10, 40, 56, and 100 Gigabit Infiniband (IB)/Ethernet adapters.</p> - <p>Remote Direct Memory Access (RDMA) has been shown to have a + <p>Remote Direct Memory Access (RDMA) has been shown to have great value for storage applications. RDMA infrastructure provides benefits such as zero-copy, CPU offload, reliable transport, fabric consolidation, and many more. The iSER @@ -2584,7 +2584,7 @@ Deputy Security Officer. Accordingly, the role of the SO team has been redefined to be the controller of the distribution of security sensitive information into and - within the project; they are responsible for interfacing + within the project: they are responsible for interfacing with external bodies and individuals reporting security problems to the project, and connecting those reports to the appropriate individuals within the project with the @@ -2616,8 +2616,9 @@ for other (Tier 2 or below) architectures is not yet of sufficient quality to be viable, and the older but pre-existing GPLv2 toolchain cannot support some of the - interesting new architectures such as arm64 and RISC V. - Pragmatically, in order for the project to support these, + interesting new architectures such as arm64 and RISC-V. + Pragmatically, in order for the project to support + these architectures, until LLVM support arrives we must turn to the GNU project's GPLv3 licenced toolchain.</p> @@ -2668,9 +2669,9 @@ authorial attributions for sections of documentation, some of which may only be a few words long. Unlike source code, blocks of documentation are frequently moved around within - individual files, or even between files. Consequently Core - would like to introduce a "Voluntary Contribution - Agreement" along the lines of the one operated by the + individual files, or even between files. Consequently, Core + would like to introduce a Voluntary Contribution + Agreement along the lines of the one operated by the Apache Foundation. With this, copyrights are signed over to the &os; Foundation, with individual contributions being recognised by recording names in a general @@ -2721,7 +2722,7 @@ <p>No commit bits were taken in during the quarter. A non-committer account was approved for Kevin Bowling of LimeLight Networks. Kevin will be doing systems - administration work with clusteradm with particular interest + administration work with clusteradm, with particular interest in the parts of the cluster that are now hosted in LLNW's facilities. Deb Goodkin of the &os; Foundation was added to the developers mailing list: she was one of the few members of @@ -3504,7 +3505,8 @@ can generate a sequence of commands to check out the ports tree from Subversion, apply the patch, and then invoke <tt>poudriere</tt> to build the affected part of the ports - tree. Ricky consulted with Torsten Zühlsdorff on this. + tree. Ricky consulted with Torsten Zühlsdorff + during its development. This script will be used later to test changes to the ports tree.</li> @@ -3577,7 +3579,7 @@ <li>Michael Zhilin fixed the Akuma library for &os;. The Akuma library is used by Jenkins to determine what command-line arguments were passed to a running process. To - fix this, Michael invoked an &os;-specific <tt>sysctl()</tt> + fix it, Michael invoked an &os;-specific <tt>sysctl()</tt> with KERN_PROC_ARGS to determine the arguments for a running pid. This fix allows a running Jenkins instance to restart itself after new plugins are installed.</li> @@ -4207,7 +4209,7 @@ <tt>loader(8)</tt>. Other devices may be loaded there, or early in the boot (depending on which gives better performance). Users will still be able to run more - "monolithic" configurations, as well as limit which + monolithic; configurations, as well as limit which kernel modules are available as can be done today, though without the convenience that automatic loading will provide. This work remains ongoing.</p> @@ -4316,7 +4318,7 @@ 28th and a 29th (from PC-BSD 10.2) added. Items crossed off by version 1.24 include (amongst others) <tt>mfs</tt> support for <tt>/tmp</tt>, static ARP and networking, persistent - "entropy" for the randomness subsystem, + entropy for the randomness subsystem, <tt>pefs</tt>, and <tt>hald</tt>.</p> <p>The remaining items in the task list are mostly aimed at
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201602010601.u1161EeX057424>