Date: Wed, 13 Apr 2016 01:18:28 +0000 (UTC) From: Warren Block <wblock@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r48605 - head/en_US.ISO8859-1/htdocs/news/status Message-ID: <201604130118.u3D1ISge023000@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: wblock Date: Wed Apr 13 01:18:27 2016 New Revision: 48605 URL: https://svnweb.freebsd.org/changeset/doc/48605 Log: Whitespace-only cleanup, translators please ignore. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-01-2016-03.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-01-2016-03.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2016-01-2016-03.xml Wed Apr 13 01:02:36 2016 (r48604) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2016-01-2016-03.xml Wed Apr 13 01:18:27 2016 (r48605) @@ -26,13 +26,13 @@ 2016.</p> <p>The first quarter of 2016 was another productive quarter for - the &os; project and community. [...]</p> + the &os; project and community. [...]</p> <p>Thanks to all the reporters for the excellent work!</p> <p>The deadline for submissions covering the period from April to June 2016 is July 7, 2016.</p> - ?> + ?> </section> <category> @@ -210,11 +210,12 @@ <body> - <p>A new <tt>-manage-gids</tt> option was added to the <tt>nfsuserd</tt> - daemon. This option tells the NFS server to use the list of - groups for a uid on the server and not the list of groups in - the NFS RPC request. Use of this option avoids the 16 group - limit for NFS RPCs using AUTH_SYS (the default).</p> + <p>A new <tt>-manage-gids</tt> option was added to the + <tt>nfsuserd</tt> daemon. This option tells the NFS server to + use the list of groups for a uid on the server and not the + list of groups in the NFS RPC request. Use of this option + avoids the 16 group limit for NFS RPCs using AUTH_SYS (the + default).</p> <p>Work is ongoing with respect to development of pNFS support for the NFS server using GlusterFS as a back end. This will @@ -269,10 +270,11 @@ <help> <task> - <p>Potentially optimizing <tt>setjmp</tt>/<tt>longjmp</tt> to not use SPE unless - it has already been enabled. This would save the kernel - switch for processes that do not otherwise use the SPE. This - is a low priority task which may not be completed.</p> + <p>Potentially optimizing <tt>setjmp</tt>/<tt>longjmp</tt> to + not use SPE unless it has already been enabled. This would + save the kernel switch for processes that do not otherwise + use the SPE. This is a low priority task which may not be + completed.</p> </task> </help> </project> @@ -300,7 +302,7 @@ <body> <p>The major news for this quarter is the update of the i915 driver in the kernel! The driver now matches Linux 3.8.13, so - it includes initial Haswell support. Linux 3.8 is already + it includes initial Haswell support. Linux 3.8 is already three years old, but work continues to upgrade DRM further. In particular, the move to <tt>linuxkpi</tt> was started.</p> @@ -311,7 +313,7 @@ <p>We attended FOSDEM 2016 in Brussels. Jean-Sébastien Pédron gave a talk to explain the work of the graphics team and show - how people can contribute. It was well received and the + how people can contribute. It was well received and the presentation was followed by interesting discussions. FOSDEM was also a nice occasion to meet and talk again to the nice "upstream" developers of the graphics stack.</p> @@ -495,17 +497,18 @@ <body> <p>Since the last report &os; support for ThunderX has been - significantly improved and stabilized. Semihalf contributions + significantly improved and stabilized. Semihalf contributions include the following items:</p> <ul> <li>Support for the newest ThunderX chip revisions (Pass 2.0) - and current Cavium firmware. Backward compatibility is + and current Cavium firmware. Backward compatibility is maintained.</li> - <li>Moved to using <tt>pci_host_generic.c</tt> as a main driver for the - internal PCIe bridge. Significant rework of PCIe code to - support both generic and ThunderX based platforms. </li> + <li>Moved to using <tt>pci_host_generic.c</tt> as a main + driver for the internal PCIe bridge. Significant rework of + PCIe code to support both generic and ThunderX based + platforms.</li> <li> Serious networking performance boost and bug fixes: </li> <ul> @@ -531,8 +534,8 @@ <ul> <li>Significantly improved overall I/O performance:</li> <ul> - <li>Complete rework of <tt>copyin</tt>/<tt>copyout</tt> and <tt>bzero</tt> - functionalities</li> + <li>Complete rework of <tt>copyin</tt>/<tt>copyout</tt> and + <tt>bzero</tt> functionalities</li> </ul> <li>Other improvements:</li> @@ -639,14 +642,15 @@ hotplug is present at the URL above. Much of the new code lives in the PCI-PCI bridge driver to handle hotplug events and manage the PCI-express slot registers. Additional changes - in the branch include adding new <tt>rescan</tt> and <tt>delete</tt> - commands to <tt>devctl(8)</tt> as well as support for - rescanning PCI busses.</p> + in the branch include adding new <tt>rescan</tt> and + <tt>delete</tt> commands to <tt>devctl(8)</tt> as well as + support for rescanning PCI busses.</p> <p>The current implementation has been tested on systems with ExpressCard but could use additional testing, especially on systems with other PCI-express HotPlug features such as - mechanical latches, attention buttons, indicators, and so on.</p> + mechanical latches, attention buttons, indicators, and so + on.</p> </body> <help> @@ -684,9 +688,9 @@ that the experience of KDE and Qt on FreeBSD is as good as possible.</p> - <p>While the list of updates is shorter than that for the previous - quarter, the team remained busy and work on KDE Frameworks 5 - and Plasma 5 continues.</p> + <p>While the list of updates is shorter than that for the + previous quarter, the team remained busy and work on KDE + Frameworks 5 and Plasma 5 continues.</p> <p>Tobias Berner, who has been driving our KDE Frameworks 5 and Plasma 5 efforts from the beginning, received @@ -729,9 +733,9 @@ <p>Users interested in testing those ports are encouraged to follow the instructions in <a href="https://freebsd.kde.org/area51.php">our website</a> - and report their results to our mailing list. Qt5 5.6.0 is in - our <tt>qt-5.6</tt> branch, and Plasma 5 and the rest is in the - <tt>plasma5</tt> branch.</p> + and report their results to our mailing list. Qt5 5.6.0 is in + our <tt>qt-5.6</tt> branch, and Plasma 5 and the rest is in + the <tt>plasma5</tt> branch.</p> </body> <help> @@ -792,7 +796,7 @@ real lock structures.</p> <p>New umtx operations to create or look up the shared object, - by the memory key, were added. Libthr is modified to lookup + by the memory key, were added. Libthr is modified to lookup the object and use it for shared locks, instead of using malloc() as for private locks.</p> @@ -894,10 +898,10 @@ switch.</p> <p>There is an ongoing progress to remove Rails 3.2 from the - ports tree. While many gems already work with the new version, - there are some exceptions. For example www/redmine needs a big - update (which is currently tested) because it depends on gems - which therefore depends on Rails 3.2.</p> + ports tree. While many gems already work with the new + version, there are some exceptions. For example www/redmine + needs a big update (which is currently tested) because it + depends on gems which therefore depends on Rails 3.2.</p> <p>If you want to help porting or testing, feel free to contact me or the mailinglist <tt>ruby@FreeBSD.org</tt>.</p> @@ -920,10 +924,10 @@ <body> <p>After nearly a year of work on this project, GitLab 8.5.5 was - committed into the ports tree. A big thanks to the enormous + committed into the ports tree. A big thanks to the enormous number of people involved! Since GitLab is a fast moving project, there is also ongoing work to stay in sync with - upstream. Have fun!</p> + upstream. Have fun!</p> </body> </project> @@ -948,10 +952,10 @@ <ul> <li><tt>WITH_FAST_DEPEND</tt> was made default in r296668 and later made the only option in r297434. The new depend code - avoids a <tt>make depend</tt> tree walk and generates <tt>.depend</tt> files - during build as a side-effect of compiling. This is using - the <tt>-MF</tt> flags of the compiler. This speeds up the build by - 15-35%.</li> + avoids a <tt>make depend</tt> tree walk and generates + <tt>.depend</tt> files during build as a side-effect of + compiling. This is using the <tt>-MF</tt> flags of the + compiler. This speeds up the build by 15-35%.</li> <li><a href="http://bugs.freebsd.org/196193">PR 196193</a>: <tt>WITHOUT_CROSS_COMPILER</tt> was fixed to properly use @@ -979,11 +983,12 @@ <task> <p>Enabling <tt>WITH_META_MODE</tt> in buildworld to provide a - reliable incremental build using <tt>filemon(4)</tt> and <tt>bmake</tt>'s - <tt>.MAKE.MODE=meta</tt>. This should not be confused with - <tt>WITH_DIRDEPS_BUILD</tt> which previously was named - <tt>WITH_META_MODE</tt> and is a drastically different build - system presented at BSDCan 2014 by Simon Gerraty.</p> + reliable incremental build using <tt>filemon(4)</tt> and + <tt>bmake</tt>'s <tt>.MAKE.MODE=meta</tt>. This should not + be confused with <tt>WITH_DIRDEPS_BUILD</tt> which + previously was named <tt>WITH_META_MODE</tt> and is a + drastically different build system presented at BSDCan 2014 + by Simon Gerraty.</p> </task> </help> </project> @@ -1013,24 +1018,25 @@ <body> <p>Filemon is a kernel module for tracing which files a command creates, reads, writes, or executes. It allows tracking build - dependencies in combination with <tt>bmake</tt>'s meta mode. <tt>bmake</tt> - stores filemon's output in a <tt>.meta</tt> file along with the - build command and later uses this to trigger a rebuild of the target if any of the files - referenced are missing or modified or if the build command - changes. It provides the - same functionality as compiler <tt>-MF</tt> flags but for everything. - It will be critical for buildworld's <tt>WITH_META_MODE</tt> - (which is the normal buildworld but just using filemon) to - provide a reliable incremental build without even the need of - <tt>.depend</tt> files or compiler <tt>-MF</tt> flags. This allows - <tt>-DNO_CLEAN</tt> to work all of the time.</p> + dependencies in combination with <tt>bmake</tt>'s meta mode. + <tt>bmake</tt> stores filemon's output in a <tt>.meta</tt> + file along with the build command and later uses this to + trigger a rebuild of the target if any of the files referenced + are missing or modified or if the build command changes. It + provides the same functionality as compiler <tt>-MF</tt> flags + but for everything. It will be critical for buildworld's + <tt>WITH_META_MODE</tt> (which is the normal buildworld but + just using filemon) to provide a reliable incremental build + without even the need of <tt>.depend</tt> files or compiler + <tt>-MF</tt> flags. This allows <tt>-DNO_CLEAN</tt> to work + all of the time.</p> - <p>Filemon on -HEAD was improved for stability - and performance over this quarter. It no longer causes every syscall it hooks + <p>Filemon on -HEAD was improved for stability and performance + over this quarter. It no longer causes every syscall it hooks into to loop on processes looking for a matching filemon struct. It now just attaches directly to the struct proc with its own pointer. This improves performance by reducing lock - contention during a build. Much other work went into + contention during a build. Much other work went into improving error handling and other stability issues in the module as well.</p> @@ -1088,9 +1094,9 @@ peripherals.</p> <p>Currently most code is checked in to enable basic support: - dTSEC (ethernet), core support (e500mc, e5500). - As part of this, <tt>rman</tt>, the kernel resource manager, was - enhanced to use <tt>uintmax_t</tt> for resources. This allows devices + dTSEC (ethernet), core support (e500mc, e5500). As part of + this, <tt>rman</tt>, the kernel resource manager, was enhanced + to use <tt>uintmax_t</tt> for resources. This allows devices to be physically above the 4GB boundary on 32-bit systems. With a statically compiled device tree, it boots to multiuser mode with nfsroot, and can be used as normal (serial and SSH @@ -1104,15 +1110,15 @@ <help> <task> <p>eSDHC driver: Work has been started on this, hijacking the - <tt>imx_sdhc.c</tt> from Ian Lepore, but there are still bugs: - missing DMA from the iMX driver, and odd timeouts after the - system starts up.</p> + <tt>imx_sdhc.c</tt> from Ian Lepore, but there are still + bugs: missing DMA from the iMX driver, and odd timeouts + after the system starts up.</p> </task> <task> <p>SATA support: There is a WIP driver for the SATA controller, but it is currently very slow, about 11MB/s on a - SATA 2 link. It currently relies on a 10ms delay on every + SATA 2 link. It currently relies on a 10ms delay on every SATA transaction for it to be even somewhat stable. Without this delay, the disk scan never works and I have not yet figured out why.</p> @@ -1126,7 +1132,7 @@ <task> <p>64-bit support: The CPU on the board is a P5020, a 64-bit - e5500 dual-core SoC. Currently, booke support in FreeBSD is + e5500 dual-core SoC. Currently, booke support in FreeBSD is 32-bit only.</p> </task> @@ -1210,8 +1216,8 @@ ways to translate like the PO/gettext-based system. We are always looking for volunteers who are interested in translating small sections or even entire documents. The - process is relatively easy and contributors do not have to know - much to get started. The members of the FreeBSD German + process is relatively easy and contributors do not have to + know much to get started. The members of the FreeBSD German Documentation Team are also willing to mentor people who are interested in helping out.</p> </body> @@ -1251,13 +1257,13 @@ <p>The ELF Tool Chain project released version 0.7.1 in February. We have been tracking snapshots of the upstream repository in &os; and are not blocked waiting for releases to - update. Having an official release brings the benefit of + update. Having an official release brings the benefit of broader testing and visibility within other open source projects.</p> <p>In the first quarter of 2016 The ELF Tool Chain tools were updated to a snapshot of upstream SVN revision 3400, which - is close to the 0.7.1 release. Additional bug fixes were + is close to the 0.7.1 release. Additional bug fixes were committed to FreeBSD and subsequently merged into the upstream repository.</p> @@ -1367,10 +1373,10 @@ <p>When &os; virtual machines (VMs) run on Hyper-V, using Hyper-V synthetic devices is recommended to get the best network and storage performance and make full use of all the - benefits that Hyper-V provides. The collection of drivers that - are required to use Hyper-V synthetic devices in FreeBSD are - known as FreeBSD Integration Services (BIS). Some of the BIS - drivers (like network and storage drivers) have existed in + benefits that Hyper-V provides. The collection of drivers + that are required to use Hyper-V synthetic devices in FreeBSD + are known as FreeBSD Integration Services (BIS). Some of the + BIS drivers (like network and storage drivers) have existed in FreeBSD 9.x and 10.x for years, but there are still some performance and stability issues and bugs. Compared with Windows and Linux VMs, the current BIS lacks some useful @@ -1378,10 +1384,11 @@ support for UEFI VM (boot from UEFI), etc.</p> <p>During the past quarter, we made a great progress on the - performance tuning for Hyper-V network driver. We also + performance tuning for Hyper-V network driver. We also refactored and cleaned up the VMBus driver, and fixed some - important bugs. All the work makes FreeBSD VMs run even better - on Hyper-V and the Hyper-V based cloud platform Azure!</p> + important bugs. All the work makes FreeBSD VMs run even + better on Hyper-V and the Hyper-V based cloud platform + Azure!</p> <p>Our work during 2016Q1 is documented below:</p> @@ -1389,12 +1396,12 @@ <ul> <li>We added the LRO (Large Receive Offloading) support to the - driver and properly handled the ACK packets. This + driver and properly handled the ACK packets. This effectively reduced the CPU cycles used in the TCP/IP stack and dramatically boosted the network performance!</li> <li>We enabled the vRSS (virtual Receive Side Scaling) support - for the driver. This greatly improved the network + for the driver. This greatly improved the network performance for SMP virtual machine (VM).</li> <li>We used a separate Tx kernel thread to relieve the Rx @@ -1433,8 +1440,8 @@ <tt>lapic_ipi_alloc()</tt>.</li> <li>We are modularizing the Hyper-V modules: 1) they will be - loaded in the loader; 2) we are going to enhance <tt>devd(8)</tt> to - improve the hot plug case.</li> + loaded in the loader; 2) we are going to enhance + <tt>devd(8)</tt> to improve the hot plug case.</li> </ul> <p>Bug Fixing</p> @@ -1529,36 +1536,37 @@ following an inactivity period of more than 18 months (milki, brian), or on committer's request (mmoll). We had one returning committer (fluffy) who had his commit bit - reinstated. Two new developers were granted a ports commit bit - (Olivier Cochard-Labbe and Christoph Moench-Tegeder).</p> + reinstated. Two new developers were granted a ports commit + bit (Olivier Cochard-Labbe and Christoph Moench-Tegeder).</p> <p>On the management side, we had the pleasure to welcome miwi back to the portmgr team.</p> - <p>On the QA side, 39 exp-runs were performed to validate sensitive - updates or cleanups. The most noticeable change might be the - removal of the now unneeded <tt>${PORTSDIR}</tt> when - specifying dependencies in Makefiles (see the - <tt>/usr/ports/CHANGES</tt> entry dated 20160402). Amongst - other noticeable changes are the update to ruby 2.3, ruby-gems - to 2.5.1, CMake to 3.5.0, clang to 3.8.0-r258968, Qt5 to - 5.5.1, Gnome to 3.18, boost to 1.60.0, the update of libc++ in - base to 3.8.0 release, and the enabling of LLVM libunwind by - default on x86. The CentOS ports were also updated. Some - infrastructure changes included the switch from - <tt>bsd.gnome.mk</tt> and <tt>bsd.mate.mk</tt> to the simpler - <tt>Uses/gnome.mk</tt> and <tt>Uses/mate.mk</tt>. Some work - was also done to improve poudriere builds by reducing - dependency calculation and general overheads.</p> + <p>On the QA side, 39 exp-runs were performed to validate + sensitive updates or cleanups. The most noticeable change + might be the removal of the now unneeded + <tt>${PORTSDIR}</tt> when specifying dependencies in + Makefiles (see the <tt>/usr/ports/CHANGES</tt> entry dated + 20160402). Amongst other noticeable changes are the update to + ruby 2.3, ruby-gems to 2.5.1, CMake to 3.5.0, clang to + 3.8.0-r258968, Qt5 to 5.5.1, Gnome to 3.18, boost to 1.60.0, + the update of libc++ in base to 3.8.0 release, and the + enabling of LLVM libunwind by default on x86. The CentOS + ports were also updated. Some infrastructure changes included + the switch from <tt>bsd.gnome.mk</tt> and <tt>bsd.mate.mk</tt> + to the simpler <tt>Uses/gnome.mk</tt> and + <tt>Uses/mate.mk</tt>. Some work was also done to improve + poudriere builds by reducing dependency calculation and + general overheads.</p> </body> <help> <task> <p>We would like to remind everyone that the ports tree is built and run by volunteers, and any help is greatly - appreciated. A great amount of effort was spent on the ports - front in Q1, which allowed us to decrease the number of - pending problem reports significantly, as well as on the + appreciated. A great amount of effort was spent on the + ports front in Q1, which allowed us to decrease the number + of pending problem reports significantly, as well as on the ports infrastructure. Many thanks to all who contributed!</p> </task> @@ -1641,7 +1649,7 @@ <p>The paxtest results for the run with the previous version 5 of the patch applied and aggresively tuned can be seen at the - https://www.kib.kiev.ua/kib/aslr/paxtest.log . For + https://www.kib.kiev.ua/kib/aslr/paxtest.log . For comparison, the run on Fedora 23 on the same machine is at https://www.kib.kiev.ua/kib/aslr/fedora.log .</p> @@ -1744,10 +1752,10 @@ </links> <body> - <p>Qt 5.6 is a great framework to build embedded GUI applications, - so when Qt 5.6 was released it was natural to bring it up on - Raspberry Pi. Current Qt support in ports is very - Xorg-centric so as a proof of concept I created an + <p>Qt 5.6 is a great framework to build embedded GUI + applications, so when Qt 5.6 was released it was natural to + bring it up on Raspberry Pi. Current Qt support in ports is + very Xorg-centric so as a proof of concept I created an experimental qt56-base and qt56-multimedia.</p> <p>qt56-base can be configured for a generic ARM device with the @@ -1800,8 +1808,9 @@ <p>The proposed patch add this functionality to ubldr. The user can specify a comma-separated list of overlays as U-Boot or - the loader <tt>fdt_overlays</tt> variable and ubldr will load them from - the <tt>/boot/dtb/</tt> directory and do the overlaying.</p> + the loader <tt>fdt_overlays</tt> variable and ubldr will load + them from the <tt>/boot/dtb/</tt> directory and do the + overlaying.</p> </body> </project> @@ -1827,13 +1836,13 @@ <body> <p>The goal of this project is to reimplement the existing - MMC/SD stack using the CAM framework. This will permit + MMC/SD stack using the CAM framework. This will permit utilizing the well-tested CAM locking model and debug - features. It will also be possible to process interrupts + features. It will also be possible to process interrupts generated by the inserted card, which is a prerequisite for - implementing the SDIO interface. SDIO support is necessary for - communicating with WiFi/BT modules found on many development - boards, like Wan Raspberry Pi 3.</p> + implementing the SDIO interface. SDIO support is necessary + for communicating with WiFi/BT modules found on many + development boards, like Wan Raspberry Pi 3.</p> <p>Another feature that the new stack will have is support for sending SD commands from the userland applications using @@ -1841,15 +1850,15 @@ userland and make debugging much easier.</p> <p>The first version of the code was uploaded to Phabricator for - review. The new stack is able to attach to the SD card and + review. The new stack is able to attach to the SD card and bring it to an operational state so it is possible to read and write to the card.</p> - <p>Support for the <tt>imx_sdhci</tt> SD Host Controller (used on - iMX-based boards, for example Wandboard) was added in 2016Q1, - along with <tt>ti_sdhci</tt>, which is used on the BeagleBone Black. - Modifying other SDHCI-compliant drivers should not be - difficult.</p> + <p>Support for the <tt>imx_sdhci</tt> SD Host Controller (used + on iMX-based boards, for example Wandboard) was added in + 2016Q1, along with <tt>ti_sdhci</tt>, which is used on the + BeagleBone Black. Modifying other SDHCI-compliant drivers + should not be difficult.</p> </body> <help>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201604130118.u3D1ISge023000>