<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/fs/ext4/ext4_sb.h, branch master</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=master</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2009-05-03T20:33:44Z</updated>
<entry>
<title>ext4: Move the ext4_sb.h header file into ext4.h</title>
<updated>2009-05-03T20:33:44Z</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2009-05-03T20:33:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=ca0faba0e8ac844dc0279825eb8db876b5962ea5'/>
<id>urn:sha1:ca0faba0e8ac844dc0279825eb8db876b5962ea5</id>
<content type='text'>
There is no longer a reason for a separate ext4_sb.h header file, so
move it into ext4.h just to make life easier for developers to find
the relevant data structures and typedefs.  Should also speed up
compiles slightly, too.

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: Replace lock/unlock_super() with an explicit lock for resizing</title>
<updated>2009-04-26T02:53:39Z</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2009-04-26T02:53:39Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=32ed5058ce90024efcd811254b4b1de0468099df'/>
<id>urn:sha1:32ed5058ce90024efcd811254b4b1de0468099df</id>
<content type='text'>
    
Use a separate lock to protect s_groups_count and the other block
group descriptors which get changed via an on-line resize operation,
so we can stop overloading the use of lock_super().
    
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;

</content>
</entry>
<entry>
<title>ext4: Replace lock/unlock_super() with an explicit lock for the orphan list</title>
<updated>2009-04-26T02:54:04Z</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2009-04-26T02:54:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3b9d4ed26680771295d904a6b83e88e620780893'/>
<id>urn:sha1:3b9d4ed26680771295d904a6b83e88e620780893</id>
<content type='text'>
Use a separate lock to protect the orphan list, so we can stop
overloading the use of lock_super().

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: Add sysfs support</title>
<updated>2009-03-31T13:10:09Z</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2009-03-31T13:10:09Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=3197ebdb130473a92760100cbfe0d7e671838f48'/>
<id>urn:sha1:3197ebdb130473a92760100cbfe0d7e671838f48</id>
<content type='text'>
Add basic sysfs support so that information about the mounted
filesystem and various tuning parameters can be accessed via
/sys/fs/ext4/&lt;dev&gt;/*.

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: Track lifetime disk writes</title>
<updated>2009-03-01T00:39:58Z</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2009-03-01T00:39:58Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=afc32f7ee9febc020c73da61402351d4c90437f3'/>
<id>urn:sha1:afc32f7ee9febc020c73da61402351d4c90437f3</id>
<content type='text'>
Add a new superblock value which tracks the lifetime amount of writes
to the filesystem.  This is useful in estimating the amount of wear on
solid state drives (SSD's) caused by writes to the filesystem.

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: allocate -&gt;s_blockgroup_lock separately</title>
<updated>2009-02-15T23:07:52Z</updated>
<author>
<name>Pekka Enberg</name>
<email>penberg@cs.helsinki.fi</email>
</author>
<published>2009-02-15T23:07:52Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=705895b61133ef43d106fe6a6bbdb2eec923867e'/>
<id>urn:sha1:705895b61133ef43d106fe6a6bbdb2eec923867e</id>
<content type='text'>
As spotted by kmemtrace, struct ext4_sb_info is 17664 bytes on 64-bit
which makes it a very bad fit for SLAB allocators.  The culprit of the
wasted memory is -&gt;s_blockgroup_lock which can be as big as 16 KB when
NR_CPUS &gt;= 32.

To fix that, allocate -&gt;s_blockgroup_lock, which fits nicely in a order 2
page in the worst case, separately.  This shinks down struct ext4_sb_info
enough to fit a 2 KB slab cache so now we allocate 16 KB + 2 KB instead of
32 KB saving 14 KB of memory.

Acked-by: Andreas Dilger &lt;adilger@sun.com&gt;
Signed-off-by: Pekka Enberg &lt;penberg@cs.helsinki.fi&gt;
Cc: &lt;linux-ext4@vger.kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: Remove stale block allocator references from ext4.h</title>
<updated>2009-02-06T21:23:37Z</updated>
<author>
<name>Mike Snitzer</name>
<email>snitzer@gmail.com</email>
</author>
<published>2009-02-06T21:23:37Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=074ca44283bf031678e67af7d82668bb03c55a55'/>
<id>urn:sha1:074ca44283bf031678e67af7d82668bb03c55a55</id>
<content type='text'>
Remove some leftovers from when the old block allocator was removed
(c2ea3fde).  ext4_sb_info is now a bit lighter.  Also remove a dangling
read_block_bitmap() prototype.

Signed-off-by: Mike Snitzer &lt;snitzer@gmail.com&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: add fsync batch tuning knobs</title>
<updated>2009-01-04T01:27:38Z</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2009-01-04T01:27:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=30773840c19cea60dcef39545960d541b1ac1cf8'/>
<id>urn:sha1:30773840c19cea60dcef39545960d541b1ac1cf8</id>
<content type='text'>
Add new mount options, min_batch_time and max_batch_time, which
controls how long the jbd2 layer should wait for additional filesystem
operations to get batched with a synchronous write transaction.

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: Widen type of ext4_sb_info.s_mb_maxs[]</title>
<updated>2008-12-17T05:48:39Z</updated>
<author>
<name>Yasunori Goto</name>
<email>y-goto@jp.fujitsu.com</email>
</author>
<published>2008-12-17T05:48:39Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=ff7ef329b268b603ea4a2303241ef1c3829fd574'/>
<id>urn:sha1:ff7ef329b268b603ea4a2303241ef1c3829fd574</id>
<content type='text'>
I chased the cause of following ext4 oops report which is tested on
ia64 box.

http://bugzilla.kernel.org/show_bug.cgi?id=12018

The cause is the size of s_mb_maxs array that is defined as "unsigned
short" in ext4_sb_info structure.  If the file system's block size is
8k or greater, an unsigned short is not wide enough to contain the
value fs-&gt;blocksize &lt;&lt; 3.

Signed-off-by: Yasunori Goto &lt;y-goto@jp.fujitsu.com&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
Cc: Li Zefan &lt;lizf@cn.fujitsu.com&gt;
Cc: Miao Xie &lt;miaox@cn.fujitsu.com&gt;
Cc: stable@kernel.org
</content>
</entry>
<entry>
<title>ext4: Add support for non-native signed/unsigned htree hash algorithms</title>
<updated>2008-10-28T17:21:44Z</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2008-10-28T17:21:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=f99b25897a86fcfff9140396a97261ae65fed872'/>
<id>urn:sha1:f99b25897a86fcfff9140396a97261ae65fed872</id>
<content type='text'>
The original ext3 hash algorithms assumed that variables of type char
were signed, as God and K&amp;R intended.  Unfortunately, this assumption
is not true on some architectures.  Userspace support for marking
filesystems with non-native signed/unsigned chars was added two years
ago, but the kernel-side support was never added (until now).

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