os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Some typo and grammar fixes.

Browse source
This commit is contained in:
Christian Brueffer 2006-07-17 10:09:26 +00:00
parent be320ab292
commit ace0a6eca0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=28314
2 changed files with 32 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

32
en/news/status/report-2006-04-2006-06.xml
View file

@ -44,7 +44,7 @@
and hope to receive a status report from you next time.</p> and hope to receive a status report from you next time.</p>
<p>Thanks to all reporters for your excellent work and timing!. Enjoy <p>Thanks to all reporters for your excellent work and timing! Enjoy
reading.</p> reading.</p>
</section> </section>
@ -660,14 +660,14 @@
<body> <body>
<p>GJournal is a GEOM class which provides journaling for GEOM <p>GJournal is a GEOM class which provides journaling for GEOM
providers. It can also be used to journal various file system with providers. It can also be used to journal various file systems with
just a minimal filesystem-specific portion of code. Currently only just a minimal filesystem-specific portion of code. Currently only
UFS journaling is implemented on top of gjournal. Being UFS journaling is implemented on top of gjournal. Being
filesystem-independent and operating below the file system level, filesystem-independent and operating below the file system level,
gjournal has no way to distinguish data from metadata, thus it gjournal has no way to distinguish data from metadata, thus it
journal both. One of the nice things about gjournal is that it journals both. One of the nice things about gjournal is that it
works reliable even on disks with enabled write cache, which is works reliable even on disks with enabled write cache, which is
often not the case for journalled file system. And remember... fsck often not the case for journalled file systems. And remember... fsck
no more.</p> no more.</p>
</body> </body>
@ -709,7 +709,7 @@
example 4 MB) and allocated (committed) to the virtual device on example 4 MB) and allocated (committed) to the virtual device on
as-needed basis.</p> as-needed basis.</p>
<p>Development has started and progressing as planned (though a <p>Development has started and is progressing as planned (though a
little bit slow). Metadata format and virtual storage allocation little bit slow). Metadata format and virtual storage allocation
formats have been defined and more serious coding is in formats have been defined and more serious coding is in
progress.</p> progress.</p>
@ -1100,7 +1100,7 @@
much Hungarian resource to make these up to date.</task> much Hungarian resource to make these up to date.</task>
<task>There's a rendering issue when browsing the pages with <task>There's a rendering issue when browsing the pages with
JavaScipt enabled, but this can be server-side for me, this should JavaScript enabled, but this can be server-side for me, this should
be investigated as well.</task> be investigated as well.</task>
</help> </help>
</project> </project>
@ -1176,7 +1176,7 @@
</contact> </contact>
<body> <body>
<p>Mohan Srinivas committed his changes to make the NFSv2/3 client <p>Mohan Srinivasan committed his changes to make the NFSv2/3 client
MP safe to HEAD this quarter. Changes may be back-ported to 6.x MP safe to HEAD this quarter. Changes may be back-ported to 6.x
soon.</p> soon.</p>
@ -1186,7 +1186,7 @@
unfixed PRs against the legacy client (NFSv2/3). These are at the unfixed PRs against the legacy client (NFSv2/3). These are at the
top of his priority list. Robert is also interested in making top of his priority list. Robert is also interested in making
NFSv4-style ACLs the lingua franca for FreeBSD file systems. There NFSv4-style ACLs the lingua franca for FreeBSD file systems. There
was some discussion about integrating Rick Maclem's NFSv4 server was some discussion about integrating Rick MacKlem's NFSv4 server
into 7.x.</p> into 7.x.</p>
<p>Chuck Lever became a full source committer during this <p>Chuck Lever became a full source committer during this
@ -1872,7 +1872,7 @@
</links> </links>
<body> <body>
<p>The wireless suport has been stable for a while so most work has <p>The wireless support has been stable for a while so most work has
focused on bug fixing and improving legacy drivers.</p> focused on bug fixing and improving legacy drivers.</p>
<p>Max Laier and I worked on improving support for Intel wireless <p>Max Laier and I worked on improving support for Intel wireless
@ -1967,18 +1967,18 @@
together with a fast interrupt model dedicated to particular driver together with a fast interrupt model dedicated to particular driver
handlers that don't block on locks (i.e. serial port, clock, handlers that don't block on locks (i.e. serial port, clock,
etcetc). Unfortunately, even if the interrupt thread model proved etcetc). Unfortunately, even if the interrupt thread model proved
to be a reliable solutions, its performance were not on par with to be a reliable solution, its performance was not on par with
the pre SMPng era (4.x), and thus others solutions were the pre SMPng era (4.x), and thus others solutions were
investigated, with interrupt filtering being one of that.</p> investigated, with interrupt filtering being one of that.</p>
<p>As part of my Summer of Code 2006 work, i'm implementing <p>As part of my Summer of Code 2006 work, I'm implementing
interrupt filtering for FreeBSD, and when the framework will be in interrupt filtering for FreeBSD, and when the framework will be in
place i'll compare the performance of filters, against all the place I'll compare the performance of filters, against all the
previous models: pre-SMPng(4.x), ithread and polling.</p> previous models: pre-SMPng(4.x), ithread and polling.</p>
<p>The most important modifications to the src tree so far where: <p>The most important modifications to the src tree so far were:
<ul> <ul>
<li>made PPC accepts more than one FAST handler per irq line <li>made PPC accept more than one FAST handler per irq line
(previously INTR_FAST implied INTR_EXCL)</li> (previously INTR_FAST implied INTR_EXCL)</li>
<li>converted all the INTR_FAST handlers to be filters: return an <li>converted all the INTR_FAST handlers to be filters: return an
@ -1991,10 +1991,10 @@
<li>broke newbus API: bus_setup_intr() grew a new filter <li>broke newbus API: bus_setup_intr() grew a new filter
parameter of type "int driver_filter_t(void*)".</li> parameter of type "int driver_filter_t(void*)".</li>
<li>converted all the bus that override bus_setup_intr() to <li>converted all the buses that override bus_setup_intr() to
handle filters</li> handle filters</li>
<li>converted all the normal ithread driver to provide a NULL <li>converted all the normal ithread drivers to provide a NULL
filter funcion</li> filter funcion</li>
</ul> </ul>

32
en/news/status/report-apr-2006-jun-2006.xml
View file

@ -44,7 +44,7 @@
and hope to receive a status report from you next time.</p> and hope to receive a status report from you next time.</p>
<p>Thanks to all reporters for your excellent work and timing!. Enjoy <p>Thanks to all reporters for your excellent work and timing! Enjoy
reading.</p> reading.</p>
</section> </section>
@ -660,14 +660,14 @@
<body> <body>
<p>GJournal is a GEOM class which provides journaling for GEOM <p>GJournal is a GEOM class which provides journaling for GEOM
providers. It can also be used to journal various file system with providers. It can also be used to journal various file systems with
just a minimal filesystem-specific portion of code. Currently only just a minimal filesystem-specific portion of code. Currently only
UFS journaling is implemented on top of gjournal. Being UFS journaling is implemented on top of gjournal. Being
filesystem-independent and operating below the file system level, filesystem-independent and operating below the file system level,
gjournal has no way to distinguish data from metadata, thus it gjournal has no way to distinguish data from metadata, thus it
journal both. One of the nice things about gjournal is that it journals both. One of the nice things about gjournal is that it
works reliable even on disks with enabled write cache, which is works reliable even on disks with enabled write cache, which is
often not the case for journalled file system. And remember... fsck often not the case for journalled file systems. And remember... fsck
no more.</p> no more.</p>
</body> </body>
@ -709,7 +709,7 @@
example 4 MB) and allocated (committed) to the virtual device on example 4 MB) and allocated (committed) to the virtual device on
as-needed basis.</p> as-needed basis.</p>
<p>Development has started and progressing as planned (though a <p>Development has started and is progressing as planned (though a
little bit slow). Metadata format and virtual storage allocation little bit slow). Metadata format and virtual storage allocation
formats have been defined and more serious coding is in formats have been defined and more serious coding is in
progress.</p> progress.</p>
@ -1100,7 +1100,7 @@
much Hungarian resource to make these up to date.</task> much Hungarian resource to make these up to date.</task>
<task>There's a rendering issue when browsing the pages with <task>There's a rendering issue when browsing the pages with
JavaScipt enabled, but this can be server-side for me, this should JavaScript enabled, but this can be server-side for me, this should
be investigated as well.</task> be investigated as well.</task>
</help> </help>
</project> </project>
@ -1176,7 +1176,7 @@
</contact> </contact>
<body> <body>
<p>Mohan Srinivas committed his changes to make the NFSv2/3 client <p>Mohan Srinivasan committed his changes to make the NFSv2/3 client
MP safe to HEAD this quarter. Changes may be back-ported to 6.x MP safe to HEAD this quarter. Changes may be back-ported to 6.x
soon.</p> soon.</p>
@ -1186,7 +1186,7 @@
unfixed PRs against the legacy client (NFSv2/3). These are at the unfixed PRs against the legacy client (NFSv2/3). These are at the
top of his priority list. Robert is also interested in making top of his priority list. Robert is also interested in making
NFSv4-style ACLs the lingua franca for FreeBSD file systems. There NFSv4-style ACLs the lingua franca for FreeBSD file systems. There
was some discussion about integrating Rick Maclem's NFSv4 server was some discussion about integrating Rick MacKlem's NFSv4 server
into 7.x.</p> into 7.x.</p>
<p>Chuck Lever became a full source committer during this <p>Chuck Lever became a full source committer during this
@ -1872,7 +1872,7 @@
</links> </links>
<body> <body>
<p>The wireless suport has been stable for a while so most work has <p>The wireless support has been stable for a while so most work has
focused on bug fixing and improving legacy drivers.</p> focused on bug fixing and improving legacy drivers.</p>
<p>Max Laier and I worked on improving support for Intel wireless <p>Max Laier and I worked on improving support for Intel wireless
@ -1967,18 +1967,18 @@
together with a fast interrupt model dedicated to particular driver together with a fast interrupt model dedicated to particular driver
handlers that don't block on locks (i.e. serial port, clock, handlers that don't block on locks (i.e. serial port, clock,
etcetc). Unfortunately, even if the interrupt thread model proved etcetc). Unfortunately, even if the interrupt thread model proved
to be a reliable solutions, its performance were not on par with to be a reliable solution, its performance was not on par with
the pre SMPng era (4.x), and thus others solutions were the pre SMPng era (4.x), and thus others solutions were
investigated, with interrupt filtering being one of that.</p> investigated, with interrupt filtering being one of that.</p>
<p>As part of my Summer of Code 2006 work, i'm implementing <p>As part of my Summer of Code 2006 work, I'm implementing
interrupt filtering for FreeBSD, and when the framework will be in interrupt filtering for FreeBSD, and when the framework will be in
place i'll compare the performance of filters, against all the place I'll compare the performance of filters, against all the
previous models: pre-SMPng(4.x), ithread and polling.</p> previous models: pre-SMPng(4.x), ithread and polling.</p>
<p>The most important modifications to the src tree so far where: <p>The most important modifications to the src tree so far were:
<ul> <ul>
<li>made PPC accepts more than one FAST handler per irq line <li>made PPC accept more than one FAST handler per irq line
(previously INTR_FAST implied INTR_EXCL)</li> (previously INTR_FAST implied INTR_EXCL)</li>
<li>converted all the INTR_FAST handlers to be filters: return an <li>converted all the INTR_FAST handlers to be filters: return an
@ -1991,10 +1991,10 @@
<li>broke newbus API: bus_setup_intr() grew a new filter <li>broke newbus API: bus_setup_intr() grew a new filter
parameter of type "int driver_filter_t(void*)".</li> parameter of type "int driver_filter_t(void*)".</li>
<li>converted all the bus that override bus_setup_intr() to <li>converted all the buses that override bus_setup_intr() to
handle filters</li> handle filters</li>
<li>converted all the normal ithread driver to provide a NULL <li>converted all the normal ithread drivers to provide a NULL
filter funcion</li> filter funcion</li>
</ul> </ul>