Whitespace-only fixes, translators please ignore.

This commit is contained in:
Warren Block 2014-10-09 22:40:17 +00:00
parent 5afd8d6501
commit 01853e5bf1
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=45761

View file

@ -105,8 +105,8 @@
</links>
<body>
<p>Deficiencies in the current automounter, <tt>amd(8)</tt>, are a
recurring problem reported by many &os; users. A new
<p>Deficiencies in the current automounter, <tt>amd(8)</tt>, are
a recurring problem reported by many &os; users. A new
automounter is being developed to address these concerns.</p>
<p>The automounter is a cleanroom implementation of
@ -116,10 +116,10 @@
integrate with the Lightweight Directory Access Protocol
(LDAP) service.</p>
<p>The code is ready to use - it has been committed to 11-CURRENT
and 10-STABLE, and will ship as part of 10.1-RELEASE. There
is ongoing work on improving performance and fixing possible
bugs.</p>
<p>The code is ready to use - it has been committed to
11-CURRENT and 10-STABLE, and will ship as part of
10.1-RELEASE. There is ongoing work on improving performance
and fixing possible bugs.</p>
</body>
<sponsor>
@ -1038,27 +1038,29 @@
</links>
<body>
<p>I have written SSE/AVX-optimized versions of a few <tt>libc</tt>
routines for amd64. So far the list includes <tt>memcpy</tt>,
<tt>memset</tt>, and <tt>strlen</tt>. For each routine I have
written a simple regression test as well as performed some
simple microbenchmarks on various AMD and Intel CPUs.</p>
<p>I have written SSE/AVX-optimized versions of a few
<tt>libc</tt> routines for amd64. So far the list includes
<tt>memcpy</tt>, <tt>memset</tt>, and <tt>strlen</tt>. For
each routine I have written a simple regression test as well
as performed some simple microbenchmarks on various AMD and
Intel CPUs.</p>
<p>The simplest routine is <tt>strlen</tt> which appears to be a
general win in microbenchmarks. <tt>memcpy</tt> and
<tt>memset</tt> have proven trickier as different variants can
behave quite differently on different CPUs.</p>
<p>At present, I do not yet have a patch relative to <tt>libc</tt>. Once
I do, this will be suitable for more testing. I'd like to see
some real-world benchmarks that show measurable improvement
before pushing any of this up into the tree.</p>
<p>At present, I do not yet have a patch relative to
<tt>libc</tt>. Once I do, this will be suitable for more
testing. I'd like to see some real-world benchmarks that show
measurable improvement before pushing any of this up into the
tree.</p>
</body>
<help>
<task>
<p>Create a branch that holds a modified <tt>libc</tt> and is suitable
for testing</p>
<p>Create a branch that holds a modified <tt>libc</tt> and is
suitable for testing</p>
</task>
</help>
</project>
@ -1106,7 +1108,7 @@
None were taken in for safekeeping.</p>
<p>On the management side, tabthorpe@ decided to step down from
his portmgr duties in July. No other changes were made to the
his portmgr duties in July. No other changes were made to the
team during Q3.</p>
<p>This quarter also saw the release of the third quarterly