Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Jul 2015 20:40:17 +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: r47021 - head/en_US.ISO8859-1/htdocs/news/status
Message-ID:  <201507192040.t6JKeHYc061898@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: wblock
Date: Sun Jul 19 20:40:16 2015
New Revision: 47021
URL: https://svnweb.freebsd.org/changeset/doc/47021

Log:
  Whitespace-only fixes.  Spaces added in some places, removed in others,
  phlogistons massaged.  Any translators paying attention, please ignore.

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml	Sun Jul 19 20:27:41 2015	(r47020)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-04-2015-06.xml	Sun Jul 19 20:40:16 2015	(r47021)
@@ -350,7 +350,7 @@
       </ul>
 
       <p>Mathieu Arnold (<tt>mat@</tt>) committed
-	<a href=" https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197878">PR197878</a>,
+	<a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197878">PR197878</a>,
 	updating the Xfce section in the Porter's Handbook.</p>
 
       <p>We also follow the unstable releases (available in our
@@ -1091,11 +1091,10 @@
     </links>
 
     <body>
-      <p>A Process-Context Identifier (PCID) is a performance enhancing
-	feature of the
-	Translation Lookaside Buffer (TLB) on Intel processors,
-	introduced with the Sandy Bridge micro-architecture.  It
-	allows the TLB to
+      <p>A Process-Context Identifier (PCID) is a
+	performance-enhancing feature of the Translation Lookaside
+	Buffer (TLB) on Intel processors, introduced with the Sandy
+	Bridge micro-architecture.  It allows the TLB to
 	simultaneously cache translation information for several
 	address spaces, and gives an opportunity for the operating
 	system context switch code to avoid flushing the TLB upon
@@ -1126,23 +1125,24 @@
       <p>The new PCID implementation uses an algorithm described in
 	the U. Vahalia book "UNIX Internals: The New Frontiers".  The
 	algorithm is already used, for example, by the MIPS pmap for
-	assigning Address Space Identifiers (ASIDs) to software-managed
-        TLB entries.  The pmap
-	maintains a per-CPU generation count, which is assigned to the
-	next unused PCID when the context is activated on CPU.  TLB
-	invalidation includes resetting the generation count, which
-	causes reallocation of the PCID when a context switch is
-	performed.  As result, the new implementation issues exactly
-	the same amount of shootdown IPIs as a pmap which does not
-	utilize PCID.</p>
+	assigning Address Space Identifiers (ASIDs) to
+	software-managed TLB entries.  The pmap maintains a per-CPU
+	generation count, which is assigned to the next unused PCID
+	when the context is activated on CPU.  TLB invalidation
+	includes resetting the generation count, which causes
+	reallocation of the PCID when a context switch is performed.
+	As result, the new implementation issues exactly the same
+	amount of shootdown IPIs as a pmap which does not utilize
+	PCID.</p>
 
       <p>Another change included with the PCID rewrite is a move of
 	the address space switching code from assembler to C source,
 	making the algorithm easier to understand and validate.</p>
 
       <p>Measurements done with <tt>hwpmc(4)</tt> on a Haswell machine
-	indicated that the new implementation reduced the TLB miss rate by
-	up to 10 times, without an increase in TLB shootdown IPIs.</p>
+	indicated that the new implementation reduced the TLB miss
+	rate by up to 10 times, without an increase in TLB shootdown
+	IPIs.</p>
 
       <p>The rewrite was committed to HEAD at r282684.</p>
 
@@ -1405,9 +1405,9 @@
 	steam again.  The OpenBSM source code repository was migrated
 	from &os;'s Perforce server to GitHub.  We hope this will make
 	the code more accessible and stimulate outside contributions.
-	In addition to the repository migration, automated build testing
-	using Travis CI has been enabled, and initial steps towards a
-	new test release have been made.</p>
+	In addition to the repository migration, automated build
+	testing using Travis CI has been enabled, and initial steps
+	towards a new test release have been made.</p>
     </body>
 
     <help>
@@ -2571,9 +2571,8 @@
 
 	    <li>Worked with Colin Percival and Brad Davis on testing
 	      and refining the release build code to support building
-	      Amazon EC2 images and Vagrant images for Hashicorp Atlas,
-	      respectively.
-	      </li>
+	      Amazon EC2 images and Vagrant images for Hashicorp
+	      Atlas, respectively.</li>
 
 	    <li>Reworked the &os;/arm build code to provide a
 	      fully-native build infrastructure for the existing
@@ -2583,10 +2582,10 @@
 
 	    <li>Wrote several additional utilities to reduce human
 	      error in several areas of Release Engineering, including
-	      producing the filesystem hierarchy used by the FTP mirrors,
-	      enhancements to the internal build scripts used by Release
-	      Engineering, and support for automatically uploading and
-	      publishing virtual machine images.</li>
+	      producing the filesystem hierarchy used by the FTP
+	      mirrors, enhancements to the internal build scripts used
+	      by Release Engineering, and support for automatically
+	      uploading and publishing virtual machine images.</li>
 
 	    <li>While attending BSDCan 2015, Glen worked with several
 	      developers and teams on various items, such as
@@ -2627,7 +2626,8 @@
 
     <links>
       <url href="http://wiki.FreeBSD.org/Wine">Wine wiki</url>
-      <url href="http://wiki.FreeBSD.org/i386-Wine">Wine on amd64 wiki</url>
+      <url href="http://wiki.FreeBSD.org/i386-Wine">Wine on amd64
+	wiki</url>
       <url href="http://www.winehq.org">Wine homepage</url>
     </links>
 
@@ -2639,11 +2639,12 @@
 
       <ul>
 	<li>Stable releases: 1.6.2 (1 port revision)</li>
+
 	<li>Development releases: 1.7.40 through 1.7.46</li>
       </ul>
 
-      <p>The <tt>i386-wine-devel</tt> port has packages built for amd64 for
-	&os; 8.4, 9.1+, 10.1+ and CURRENT.</p>
+      <p>The <tt>i386-wine-devel</tt> port has packages built for
+	amd64 for &os; 8.4, 9.1+, 10.1+ and CURRENT.</p>
 
       <p>Accomplishments include:</p>
 
@@ -2654,24 +2655,36 @@
 
       <p>Future development on Wine will focus on:</p>
       <ul>
-	<li>Add the <tt>getdirentries(2)</tt> patch to the <tt>wine-devel</tt> port.</li>
-	<li>Redevelop and upstream the <tt>getdirentries(2)</tt> patch.</li>
-	<li>Redevelop and upstream the kernel32 <tt>Makefile</tt> patch.</li>
-	<li>Add support to the <tt>i386-wine</tt> port for <tt>pkg</tt> 1.5 (library
-	  conflicts currently prevent support).</li>
+	<li>Add the <tt>getdirentries(2)</tt> patch to the
+	  <tt>wine-devel</tt> port.</li>
+
+	<li>Redevelop and upstream the <tt>getdirentries(2)</tt>
+	  patch.</li>
+
+	<li>Redevelop and upstream the kernel32 <tt>Makefile</tt>
+	  patch.</li>
+
+	<li>Add support to the <tt>i386-wine</tt> port for
+	  <tt>pkg</tt> 1.5 (library conflicts currently prevent
+	  support).</li>
+
 	<li>Add support for Windows 32-bit on Windows 64-bit (WoW64):
 	  <ul>
-	    <li>Reduce the <tt>i386-wine</tt> port to just the components
-	      required for WoW64.</li>
+	    <li>Reduce the <tt>i386-wine</tt> port to just the
+	      components required for WoW64.</li>
+
 	    <li>Rename the <tt>i386-wine</tt> port to
 	      <tt>wow64</tt>.</li>
-	    <li>Make the wine ports depend on the wow64 ports when built
-	      on amd64.</li>
+
+	    <li>Make the wine ports depend on the wow64 ports when
+	      built on amd64.</li>
+
 	    <li>Investigate and verify the interactions between Wine64
 	      and WoW64.</li>
+
 	    <li>Investigate possible update approaches for the
-	      wow64 ports (that have to be pre-compiled) and how updating
-	      with the wine ports will work.</li>
+	      wow64 ports (that have to be pre-compiled) and how
+	      updating with the wine ports will work.</li>
 	  </ul>
 	</li>
       </ul>
@@ -2691,7 +2704,8 @@
 
       <task>
 	<p>&os;/amd64 integration (see the
-	  <a href="http://wiki.FreeBSD.org/i386-Wine">i386-Wine wiki</a>)</p>
+	  <a href="http://wiki.FreeBSD.org/i386-Wine">i386-Wine
+	    wiki</a>)</p>
       </task>
 
       <task>
@@ -2722,25 +2736,27 @@
     </links>
 
     <body>
-      <p>The KDE on &os; team focuses on packaging and making sure that
-	the experience of KDE and Qt on &os; is as good as possible.</p>
+      <p>The KDE on &os; team focuses on packaging and making sure
+	that the experience of KDE and Qt on &os; is as good as
+	possible.</p>
 
-      <p>Brad Davis has been working on CMake resulting in an update to
-	version 3.2.3 being committed to ports.</p>
+      <p>Brad Davis has been working on CMake resulting in an update
+	to version 3.2.3 being committed to ports.</p>
 
-      <p>Overall, we have updated the following ports in this quarter:</p>
+      <p>Overall, we have updated the following ports in this
+	quarter:</p>
 
-       <ul>
-	 <li>CMake 3.2.3 (committed to ports)</li>
-	 <li>Qt 4.8.7 (committed to area51)</li>
-	 <li>Qt 5.4.1 (refinements committed to ports)</li>
-       </ul>
+      <ul>
+	<li>CMake 3.2.3 (committed to ports)</li>
+	<li>Qt 4.8.7 (committed to area51)</li>
+	<li>Qt 5.4.1 (refinements committed to ports)</li>
+      </ul>
     </body>
 
     <help>
       <task>
-	<p>Put more effort into the Qt5-related ports: KDE Frameworks 5
-	  (currently worked on by Tobias Berner) and PyQt 5.</p>
+	<p>Put more effort into the Qt5-related ports: KDE Frameworks
+	  5 (currently worked on by Tobias Berner) and PyQt 5.</p>
       </task>
     </help>
   </project>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201507192040.t6JKeHYc061898>