<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/gnu/ext2fs/ext2_linux_balloc.c, branch release/5.3.0_cvs</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 tag</title>
<updated>2004-11-04T19:12:42+00:00</updated>
<author>
<name>cvs2svn</name>
<email>cvs2svn@FreeBSD.org</email>
</author>
<published>2004-11-04T19:12:42+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=3f86d8a2ea3f3265afaa1fd263b0004c5c000e69'/>
<id>3f86d8a2ea3f3265afaa1fd263b0004c5c000e69</id>
<content type='text'>
'RELENG_5_3_0_RELEASE'.

This commit was manufactured to restore the state of the 5.3-RELEASE image.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
'RELENG_5_3_0_RELEASE'.

This commit was manufactured to restore the state of the 5.3-RELEASE image.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix the alpha tinderbox. The alpha specific bitops used by the bitmap</title>
<updated>2003-10-29T07:35:53+00:00</updated>
<author>
<name>Marcel Moolenaar</name>
<email>marcel@FreeBSD.org</email>
</author>
<published>2003-10-29T07:35:53+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=3c6441a736bf2a8c784b2355e3d69e150f73ea1d'/>
<id>3c6441a736bf2a8c784b2355e3d69e150f73ea1d</id>
<content type='text'>
code has the typical branch prediction detour, which creates cross-
section branches. A LINT kernel is apparently large enough nowadays
that the .text and .text2 sections cannot always be layed-out so that
branches between them reach.
The fix is to stop using the alpha-specific bitops and instead use
the portable implementation used by all platforms other than alpha
and i386.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
code has the typical branch prediction detour, which creates cross-
section branches. A LINT kernel is apparently large enough nowadays
that the .text and .text2 sections cannot always be layed-out so that
branches between them reach.
The fix is to stop using the alpha-specific bitops and instead use
the portable implementation used by all platforms other than alpha
and i386.
</pre>
</div>
</content>
</entry>
<entry>
<title>Change of plans: Add ext2_bitops.h with generic and portable</title>
<updated>2003-08-25T01:39:47+00:00</updated>
<author>
<name>Marcel Moolenaar</name>
<email>marcel@FreeBSD.org</email>
</author>
<published>2003-08-25T01:39:47+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=cc56683de77ecedb36bcc97300b04593964cc881'/>
<id>cc56683de77ecedb36bcc97300b04593964cc881</id>
<content type='text'>
implementations. Use those on platforms that don't have MD
headers. Remove the ia64 MD header. We're going to use the C
implementation there.

Suggested by: bde
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
implementations. Use those on platforms that don't have MD
headers. Remove the ia64 MD header. We're going to use the C
implementation there.

Suggested by: bde
</pre>
</div>
</content>
</entry>
<entry>
<title>Add compilation support for extfs on ia64, primarily to support LINT.</title>
<updated>2003-08-23T03:58:11+00:00</updated>
<author>
<name>Marcel Moolenaar</name>
<email>marcel@FreeBSD.org</email>
</author>
<published>2003-08-23T03:58:11+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=fcf18c73759fbab140e8876cd8dd297d5b0cca18'/>
<id>fcf18c73759fbab140e8876cd8dd297d5b0cca18</id>
<content type='text'>
The functions in ia64-bitops.h merely call panic() for now. They need
to be implemented some day, just not today.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The functions in ia64-bitops.h merely call panic() for now. They need
to be implemented some day, just not today.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix typos, mostly s/ an / a / where appropriate and a few s/an/and/</title>
<updated>2002-12-30T21:18:15+00:00</updated>
<author>
<name>Jens Schweikhardt</name>
<email>schweikh@FreeBSD.org</email>
</author>
<published>2002-12-30T21:18:15+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=d64ada501ae33c02e7c4e3ce21962907df814a5a'/>
<id>d64ada501ae33c02e7c4e3ce21962907df814a5a</id>
<content type='text'>
Add FreeBSD Id tag where missing.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add FreeBSD Id tag where missing.
</pre>
</div>
</content>
</entry>
<entry>
<title>Complete the separation of ext2fs from ufs by copying the remaining</title>
<updated>2002-05-16T19:08:03+00:00</updated>
<author>
<name>Ian Dowse</name>
<email>iedowse@FreeBSD.org</email>
</author>
<published>2002-05-16T19:08:03+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=9504abaad76b5fa631ac0eb7a59d107332189fbd'/>
<id>9504abaad76b5fa631ac0eb7a59d107332189fbd</id>
<content type='text'>
shared code and converting all ufs references. Originally it may
have made sense to share common features between the two filesystems,
but recently it has only caused problems, the UFS2 work being the
final straw.

All UFS_* indirect calls are now direct calls to ext2_* functions,
and ext2fs-specific mount and inode structures have been introduced.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
shared code and converting all ufs references. Originally it may
have made sense to share common features between the two filesystems,
but recently it has only caused problems, the UFS2 work being the
final straw.

All UFS_* indirect calls are now direct calls to ext2_* functions,
and ext2fs-specific mount and inode structures have been introduced.
</pre>
</div>
</content>
</entry>
<entry>
<title>Put the bits in place for Alpha support for ext2. Not tested.</title>
<updated>2000-12-09T22:32:49+00:00</updated>
<author>
<name>Matt Jacob</name>
<email>mjacob@FreeBSD.org</email>
</author>
<published>2000-12-09T22:32:49+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=80e8f27bbc411fd6dddd3d4fa8dc800d3c0678ee'/>
<id>80e8f27bbc411fd6dddd3d4fa8dc800d3c0678ee</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Support filesystems with the not-so-new "sparse_superblocks" feature.</title>
<updated>2000-11-03T16:41:48+00:00</updated>
<author>
<name>Bruce Evans</name>
<email>bde@FreeBSD.org</email>
</author>
<published>2000-11-03T16:41:48+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=e6410301f020eb4ef5f58484ef90a7a31b7fd926'/>
<id>e6410301f020eb4ef5f58484ef90a7a31b7fd926</id>
<content type='text'>
When this feature is enabled, mke2fs doesn't necessarily allocate a
super block and its associated descriptor blocks for every group.
The (non-)allocations are reflected in the block bitmap.  Since the
filesystem code doesn't write to these blocks except for the first
superblock, all it has to do to support them is to not count them in
ext2_statfs() and not attempt to check them at mount time in
ext2_check_blocks_bitmap() (the check has never been enabled in
FreeBSD anyway).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When this feature is enabled, mke2fs doesn't necessarily allocate a
super block and its associated descriptor blocks for every group.
The (non-)allocations are reflected in the block bitmap.  Since the
filesystem code doesn't write to these blocks except for the first
superblock, all it has to do to support them is to not count them in
ext2_statfs() and not attempt to check them at mount time in
ext2_check_blocks_bitmap() (the check has never been enabled in
FreeBSD anyway).
</pre>
</div>
</content>
</entry>
<entry>
<title>Weaken a bogus dependency on &lt;sys/proc.h&gt; in &lt;sys/buf.h&gt; by #ifdef'ing</title>
<updated>2000-10-29T14:54:55+00:00</updated>
<author>
<name>Poul-Henning Kamp</name>
<email>phk@FreeBSD.org</email>
</author>
<published>2000-10-29T14:54:55+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=9f69a4578a40b7ac10320af4fd2a4ac9b47012a6'/>
<id>9f69a4578a40b7ac10320af4fd2a4ac9b47012a6</id>
<content type='text'>
the offending inline function (BUF_KERNPROC) on it being #included
already.

I'm not sure BUF_KERNPROC() is even the right thing to do or in the
right place or implemented the right way (inline vs normal function).

Remove consequently unneeded #includes of &lt;sys/proc.h&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
the offending inline function (BUF_KERNPROC) on it being #included
already.

I'm not sure BUF_KERNPROC() is even the right thing to do or in the
right place or implemented the right way (inline vs normal function).

Remove consequently unneeded #includes of &lt;sys/proc.h&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Separate the struct bio related stuff out of &lt;sys/buf.h&gt; into</title>
<updated>2000-05-05T09:59:14+00:00</updated>
<author>
<name>Poul-Henning Kamp</name>
<email>phk@FreeBSD.org</email>
</author>
<published>2000-05-05T09:59:14+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.freebsd.org/src/commit/?id=9626b608de4a43ec9984c3ee95b2ce624b3c0924'/>
<id>9626b608de4a43ec9984c3ee95b2ce624b3c0924</id>
<content type='text'>
&lt;sys/bio.h&gt;.

&lt;sys/bio.h&gt; is now a prerequisite for &lt;sys/buf.h&gt; but it shall
not be made a nested include according to bdes teachings on the
subject of nested includes.

Diskdrivers and similar stuff below specfs::strategy() should no
longer need to include &lt;sys/buf.&gt; unless they need caching of data.

Still a few bogus uses of struct buf to track down.

Repocopy by:    peter
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
&lt;sys/bio.h&gt;.

&lt;sys/bio.h&gt; is now a prerequisite for &lt;sys/buf.h&gt; but it shall
not be made a nested include according to bdes teachings on the
subject of nested includes.

Diskdrivers and similar stuff below specfs::strategy() should no
longer need to include &lt;sys/buf.&gt; unless they need caching of data.

Still a few bogus uses of struct buf to track down.

Repocopy by:    peter
</pre>
</div>
</content>
</entry>
</feed>
