<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lwn.git/fs/ext4/mballoc.h, branch v4.5.3</title>
<subtitle>Linux kernel documentation tree maintained by Jonathan Corbet</subtitle>
<id>http://mirrors.hust.edu.cn/git/lwn.git/atom?h=v4.5.3</id>
<link rel='self' href='http://mirrors.hust.edu.cn/git/lwn.git/atom?h=v4.5.3'/>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/'/>
<updated>2014-02-20T18:32:10+00:00</updated>
<entry>
<title>ext4: remove unused ac_ex_scanned</title>
<updated>2014-02-20T18:32:10+00:00</updated>
<author>
<name>Eric Sandeen</name>
<email>sandeen@redhat.com</email>
</author>
<published>2014-02-20T18:32:10+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=dc9ddd984df5f5611c7e2149d19be5a8721c1ac5'/>
<id>urn:sha1:dc9ddd984df5f5611c7e2149d19be5a8721c1ac5</id>
<content type='text'>
When looking at a bug report with:

&gt; kernel: EXT4-fs: 0 scanned, 0 found

I thought wow, 0 scanned, that's odd?  But it's not odd; it's printing
a variable that is initialized to 0 and never touched again.

It's never been used since the original merge, so I don't really even
know what the original intent was, either.

If anyone knows how to hook it up, speak now via patch, otherwise just
yank it so it's not making a confusing situation more confusing in
kernel logs.

Signed-off-by: Eric Sandeen &lt;sandeen@redhat.com&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: address a benign compiler warning</title>
<updated>2014-02-18T01:50:59+00:00</updated>
<author>
<name>Patrick Palka</name>
<email>patrick@parcs.ath.cx</email>
</author>
<published>2014-02-18T01:50:59+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=024949ec8fc165bfac8eb051e537bc303adb365f'/>
<id>urn:sha1:024949ec8fc165bfac8eb051e537bc303adb365f</id>
<content type='text'>
When !defined(CONFIG_EXT4_DEBUG), mb_debug() should be defined as a
no_printk() statement instead of an empty statement in order to suppress
the following compiler warning:

fs/ext4/mballoc.c: In function ‘ext4_mb_cleanup_pa’:
fs/ext4/mballoc.c:2659:47: warning: suggest braces around empty body in an ‘if’ statement [-Wempty-body]
   mb_debug(1, "mballoc: %u PAs left\n", count);

Signed-off-by: Patrick Palka &lt;patrick@parcs.ath.cx&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: use module parameters instead of debugfs for mballoc_debug</title>
<updated>2013-02-09T21:28:20+00:00</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2013-02-09T21:28:20+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=a0b30c12297eb63e9b994164f9c0937d29b9352d'/>
<id>urn:sha1:a0b30c12297eb63e9b994164f9c0937d29b9352d</id>
<content type='text'>
There are multiple reasons to move away from debugfs.  First of all,
we are only using it for a single parameter, and it is much more
complicated to set up (some 30 lines of code compared to 3), and one
more thing that might fail while loading the ext4 module.

Secondly, as a module paramter it can be specified as a boot option if
ext4 is built into the kernel, or as a parameter when the module is
loaded, and it can also be manipulated dynamically under
/sys/module/ext4/parameters/mballoc_debug.  So it is more flexible.

Ultimately we want to move away from using mb_debug() towards
tracepoints, but for now this is still a useful simplification of the
code base.

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: remove unused macro MB_DEFAULT_MAX_GROUPS_TO_SCAN</title>
<updated>2012-08-17T14:00:17+00:00</updated>
<author>
<name>Robin Dong</name>
<email>sanbai@taobao.com</email>
</author>
<published>2012-08-17T14:00:17+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=cc6eb18d68fb52a7de65b7a318461ca600240177'/>
<id>urn:sha1:cc6eb18d68fb52a7de65b7a318461ca600240177</id>
<content type='text'>
Signed-off-by: Robin Dong &lt;sanbai@taobao.com&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: remove EXT4_MB_{BITMAP,BUDDY} macros</title>
<updated>2012-02-20T22:54:06+00:00</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2012-02-20T22:54:06+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=c5e8f3f3bc4b5e4a73b075ea7128f48c3f215168'/>
<id>urn:sha1:c5e8f3f3bc4b5e4a73b075ea7128f48c3f215168</id>
<content type='text'>
The EXT4_MB_BITMAP and EXT4_MB_BUDDY macros obfuscate more than they
provide any abstraction.   So remove them.

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: expand commit callback and</title>
<updated>2012-02-20T22:53:02+00:00</updated>
<author>
<name>Bobi Jam</name>
<email>bobijam@whamcloud.com</email>
</author>
<published>2012-02-20T22:53:02+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=18aadd47f88464928b5ce57791c2e8f9f2aaece0'/>
<id>urn:sha1:18aadd47f88464928b5ce57791c2e8f9f2aaece0</id>
<content type='text'>
The per-commit callback was used by mballoc code to manage free space
bitmaps after deleted blocks have been released.  This patch expands
it to support multiple different callbacks, to allow other things to
be done after the commit has been completed.

Signed-off-by: Bobi Jam &lt;bobijam@whamcloud.com&gt;
Signed-off-by: Andreas Dilger &lt;adilger@whamcloud.com&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: fix a typo in struct ext4_allocation_context</title>
<updated>2011-10-31T22:55:50+00:00</updated>
<author>
<name>Robin Dong</name>
<email>sanbai@taobao.com</email>
</author>
<published>2011-10-31T22:55:50+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=ff3fc1736f1967b59801ab2cf6409fc6c8556b0a'/>
<id>urn:sha1:ff3fc1736f1967b59801ab2cf6409fc6c8556b0a</id>
<content type='text'>
This patch changes "bext" to "best".

Signed-off-by: Robin Dong &lt;sanbai@taobao.com&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: teach ext4_free_blocks() about bigalloc and clusters</title>
<updated>2011-09-09T22:50:51+00:00</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2011-09-09T22:50:51+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=84130193e0e6568dfdfb823f0e1e19aec80aff6e'/>
<id>urn:sha1:84130193e0e6568dfdfb823f0e1e19aec80aff6e</id>
<content type='text'>
The ext4_free_blocks() function now has two new flags that indicate
whether a partial cluster at the beginning or the end of the block
extents should be freed or not.  That will be up the caller (i.e.,
truncate), who can figure out whether partial clusters at the
beginning or the end of a block range can be freed.

We also have to update the ext4_mb_free_metadata() and
release_blocks_on_commit() machinery to be cluster-based, since it is
used by ext4_free_blocks().

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: teach mballoc preallocation code about bigalloc clusters</title>
<updated>2011-09-09T22:48:51+00:00</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2011-09-09T22:48:51+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=53accfa9f819c80056db6f03f9c5cfa4bcba1ed8'/>
<id>urn:sha1:53accfa9f819c80056db6f03f9c5cfa4bcba1ed8</id>
<content type='text'>
In most of mballoc.c, we do everything in units of clusters, since the
block allocation bitmaps and buddy bitmaps are all denominated in
clusters.  The one place where we do deal with absolute block numbers
is in the code that handles the preallocation regions, since in the
case of inode-based preallocation regions, the start of the
preallocation region can't be relative to the beginning of the group.

So this adds a bit of complexity, where pa_pstart and pa_lstart are
block numbers, while pa_free, pa_len, and fe_len are denominated in
units of clusters.

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: convert block group-relative offsets to use clusters</title>
<updated>2011-09-09T22:46:51+00:00</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2011-09-09T22:46:51+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=3212a80a58062056bb922811071062be58d8fee1'/>
<id>urn:sha1:3212a80a58062056bb922811071062be58d8fee1</id>
<content type='text'>
Certain parts of the ext4 code base, primarily in mballoc.c, use a
block group number and offset from the beginning of the block group.
This offset is invariably used to index into the allocation bitmap, so
change the offset to be denominated in units of clusters.

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
</feed>
