<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/ufs, branch release/4.6.1</title>
<subtitle>FreeBSD source tree</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/'/>
<entry>
<title>This commit was manufactured by cvs2svn to create branch 'RELENG_4_6'.</title>
<updated>2002-07-03T13:01:42+00:00</updated>
<author>
<name>cvs2svn</name>
<email>cvs2svn@FreeBSD.org</email>
</author>
<published>2002-07-03T13:01:42+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=db0a3b09965d55f9dee7a58fb04e31df42b6ae73'/>
<id>db0a3b09965d55f9dee7a58fb04e31df42b6ae73</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Enforce a 2^31 * PAGE_SIZE file size limit to ensure that large</title>
<updated>2002-06-23T22:34:58+00:00</updated>
<author>
<name>Ian Dowse</name>
<email>iedowse@FreeBSD.org</email>
</author>
<published>2002-06-23T22:34:58+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=0f14ccf13accbc58c8bd664d2c39c56e8df714fc'/>
<id>0f14ccf13accbc58c8bd664d2c39c56e8df714fc</id>
<content type='text'>
files cannot overflow the vm_pindex_t type. This is not an MFC,
since increasing the size of vm_pindex_t as was done in -CURRENT
is not useful or appropriate for RELENG_4.

Note that on the alpha platform this change is not necessary because
vm_pindex_t is 64-bit, but limiting files to 16TB there is unlikely
to cause any problems.

Submitted by:	tegge
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
files cannot overflow the vm_pindex_t type. This is not an MFC,
since increasing the size of vm_pindex_t as was done in -CURRENT
is not useful or appropriate for RELENG_4.

Note that on the alpha platform this change is not necessary because
vm_pindex_t is 64-bit, but limiting files to 16TB there is unlikely
to cause any problems.

Submitted by:	tegge
</pre>
</div>
</content>
</entry>
<entry>
<title>MFC 1.90.  Fix a major performance issue that was introduced in late</title>
<updated>2002-06-22T18:08:04+00:00</updated>
<author>
<name>Matthew Dillon</name>
<email>dillon@FreeBSD.org</email>
</author>
<published>2002-06-22T18:08:04+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=fe11ed787ba6655374c490b9aef830240e973352'/>
<id>fe11ed787ba6655374c490b9aef830240e973352</id>
<content type='text'>
2000.  Setting B_CLRBUF for the BALLOC call unexpectedly caused BALLOC
to issue a read-before-write for each fs block, resulting in a huge
(4x) performance penalty due to extra I/Os and lack of clustering.
This workaround avoids the unnecessary read resulting in full write
clustering performance to media.  It is expected to have major visible
effects only on large news systems (e.g. INN cyclic buffers), and databases,
especially on hardware RAID systems (10x), and has already been shown to
have a huge positive effect on INN.  Most other programs use write-append
which is already optimal.

This patch does not fix the double-memory-copy to the filesystem buffer.
That is a more difficult problem and is being worked on as a separate
issue.

Reviewed by:	mckusick, tegge
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
2000.  Setting B_CLRBUF for the BALLOC call unexpectedly caused BALLOC
to issue a read-before-write for each fs block, resulting in a huge
(4x) performance penalty due to extra I/Os and lack of clustering.
This workaround avoids the unnecessary read resulting in full write
clustering performance to media.  It is expected to have major visible
effects only on large news systems (e.g. INN cyclic buffers), and databases,
especially on hardware RAID systems (10x), and has already been shown to
have a huge positive effect on INN.  Most other programs use write-append
which is already optimal.

This patch does not fix the double-memory-copy to the filesystem buffer.
That is a more difficult problem and is being worked on as a separate
issue.

Reviewed by:	mckusick, tegge
</pre>
</div>
</content>
</entry>
<entry>
<title>MFC 1.10: Minor dirhash tweaking (more aggressive cleaning, better hash).</title>
<updated>2002-04-10T21:41:14+00:00</updated>
<author>
<name>David Malone</name>
<email>dwmalone@FreeBSD.org</email>
</author>
<published>2002-04-10T21:41:14+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=44dea46f69e762e95a49ad726fad0d672ed43fe9'/>
<id>44dea46f69e762e95a49ad726fad0d672ed43fe9</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>MFC (ext2_vfsops.c 1.91, cd9660_vfsops.c 1.98, ffs_vfsops.c 1.173: set</title>
<updated>2002-04-08T09:39:30+00:00</updated>
<author>
<name>Bruce Evans</name>
<email>bde@FreeBSD.org</email>
</author>
<published>2002-04-08T09:39:30+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=f323b64ce82931cf1d7fb9c83d39ee52788c9f01'/>
<id>f323b64ce82931cf1d7fb9c83d39ee52788c9f01</id>
<content type='text'>
si_iosize_max correctly in ffs, and don't forget to set it in cd9660
and ext2fs (the original log message mistakenly said msdosfs instead of
cd9660)).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
si_iosize_max correctly in ffs, and don't forget to set it in cd9660
and ext2fs (the original log message mistakenly said msdosfs instead of
cd9660)).
</pre>
</div>
</content>
</entry>
<entry>
<title>MFC: 1.8; Fix a bug in ufsdirhash_adjfree() that caused it to</title>
<updated>2002-03-18T13:48:59+00:00</updated>
<author>
<name>Ian Dowse</name>
<email>iedowse@FreeBSD.org</email>
</author>
<published>2002-03-18T13:48:59+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=22a7513f1d071b70747796ec8601733cbad3feb4'/>
<id>22a7513f1d071b70747796ec8601733cbad3feb4</id>
<content type='text'>
incorrectly update the free-space statistics in some cases.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
incorrectly update the free-space statistics in some cases.
</pre>
</div>
</content>
</entry>
<entry>
<title>MFC b_resid KASSERT from 1.85.  This is a safety check to make sure</title>
<updated>2002-03-06T19:53:08+00:00</updated>
<author>
<name>Matthew Dillon</name>
<email>dillon@FreeBSD.org</email>
</author>
<published>2002-03-06T19:53:08+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=f63890fbeec5141faf442606b215125fe381f1e2'/>
<id>f63890fbeec5141faf442606b215125fe381f1e2</id>
<content type='text'>
that b_resid is the expected 0 value in preparation for a future commit
that will remove the b_resid calculation entirely.  It turns out that
b_resid WILL always be 0 except for the case where a write fails.  But
in the write failure case the buffer is still valid for reading and
we still want to treat it as such (as if b_resid were 0, even though it
isn't).  The filesystem code should not use b_resid in any calculations
except those involving short-read situations, and even then b_resid
will not be persistent for a VMIO backed buffer since the buffer may be
destroyed and later reconstituted, resetting b_resid to 0.  short-reads
are not used by most filesystems.  They are used by NFS only when reading
softlinks (using a non VMIO buffer). Joy.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
that b_resid is the expected 0 value in preparation for a future commit
that will remove the b_resid calculation entirely.  It turns out that
b_resid WILL always be 0 except for the case where a write fails.  But
in the write failure case the buffer is still valid for reading and
we still want to treat it as such (as if b_resid were 0, even though it
isn't).  The filesystem code should not use b_resid in any calculations
except those involving short-read situations, and even then b_resid
will not be persistent for a VMIO backed buffer since the buffer may be
destroyed and later reconstituted, resetting b_resid to 0.  short-reads
are not used by most filesystems.  They are used by NFS only when reading
softlinks (using a non VMIO buffer). Joy.
</pre>
</div>
</content>
</entry>
<entry>
<title>MFC 1.85 syntax cleanup only.</title>
<updated>2002-03-06T19:46:47+00:00</updated>
<author>
<name>Matthew Dillon</name>
<email>dillon@FreeBSD.org</email>
</author>
<published>2002-03-06T19:46:47+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=5e2b35b31b04116b522b18c1e4922e1e3cc3682f'/>
<id>5e2b35b31b04116b522b18c1e4922e1e3cc3682f</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>MFC 1.104 - fix bug where spl saved in softupdates lock could get stomped by</title>
<updated>2002-02-05T18:46:53+00:00</updated>
<author>
<name>Matthew Dillon</name>
<email>dillon@FreeBSD.org</email>
</author>
<published>2002-02-05T18:46:53+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=ac3b7de85e7232bcd3131dc1692b7473e46f23c6'/>
<id>ac3b7de85e7232bcd3131dc1692b7473e46f23c6</id>
<content type='text'>
another process.

Approved by:	mckusick
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
another process.

Approved by:	mckusick
</pre>
</div>
</content>
</entry>
<entry>
<title>MFC vfs_subr 1.338 and friends.  When downgrading a filesystem to read-only,</title>
<updated>2002-02-05T18:35:04+00:00</updated>
<author>
<name>Matthew Dillon</name>
<email>dillon@FreeBSD.org</email>
</author>
<published>2002-02-05T18:35:04+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=ae29cdc50ac9a14bfce7dc00f40b96d56811dc04'/>
<id>ae29cdc50ac9a14bfce7dc00f40b96d56811dc04</id>
<content type='text'>
operatings involving file removal and file update were not always being
fully comitted to disk, resulting in corruption.
Approved by:		mckusick
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
operatings involving file removal and file update were not always being
fully comitted to disk, resulting in corruption.
Approved by:		mckusick
</pre>
</div>
</content>
</entry>
</feed>
