<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/gfs2/sys.c, branch linux-2.6.28.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.28.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.28.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2008-09-18T12:53:59Z</updated>
<entry>
<title>GFS2: high time to take some time over atime</title>
<updated>2008-09-18T12:53:59Z</updated>
<author>
<name>Steven Whitehouse</name>
</author>
<published>2008-09-18T12:53:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=719ee344675c2efed9115934f19aa66a526b6e5b'/>
<id>urn:sha1:719ee344675c2efed9115934f19aa66a526b6e5b</id>
<content type='text'>
Until now, we've used the same scheme as GFS1 for atime. This has failed
since atime is a per vfsmnt flag, not a per fs flag and as such the
"noatime" flag was not getting passed down to the filesystems. This
patch removes all the "special casing" around atime updates and we
simply use the VFS's atime code.

The net result is that GFS2 will now support all the same atime related
mount options of any other filesystem on a per-vfsmnt basis. We do lose
the "lazy atime" updates, but we gain "relatime". We could add lazy
atime to the VFS at a later date, if there is a requirement for that
variant still - I suspect relatime will be enough.

Also we lose about 100 lines of code after this patch has been applied,
and I have a suspicion that it will speed things up a bit, even when
atime is "on". So it seems like a nice clean up as well.

From a user perspective, everything stays the same except the loss of
the per-fs atime quantum tweekable (ought to be per-vfsmnt at the very
least, and to be honest I don't think anybody ever used it) and that a
number of options which were ignored before now work correctly.

Please let me know if you've got any comments. I'm pushing this out
early so that you can all see what my plans are.

Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;
</content>
</entry>
<entry>
<title>[GFS2] Remove support for unused and pointless flag</title>
<updated>2008-07-10T15:09:29Z</updated>
<author>
<name>Steven Whitehouse</name>
</author>
<published>2008-07-10T15:09:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c9f6a6bbc284ba87337876086f7e2e6e0b0d50dd'/>
<id>urn:sha1:c9f6a6bbc284ba87337876086f7e2e6e0b0d50dd</id>
<content type='text'>
The ability to mark files for direct i/o access when opened
normally is both unused and pointless, so this patch removes
support for that feature.

Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;
</content>
</entry>
<entry>
<title>[GFS2] Remove remote lock dropping code</title>
<updated>2008-06-27T08:39:44Z</updated>
<author>
<name>Steven Whitehouse</name>
</author>
<published>2008-06-03T13:09:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1bdad606338debc6384b2844f1b53cc436b3ac90'/>
<id>urn:sha1:1bdad606338debc6384b2844f1b53cc436b3ac90</id>
<content type='text'>
There are several reasons why this is undesirable:

 1. It never happens during normal operation anyway
 2. If it does happen it causes performance to be very, very poor
 3. It isn't likely to solve the original problem (memory shortage
    on remote DLM node) it was supposed to solve
 4. It uses a bunch of arbitrary constants which are unlikely to be
    correct for any particular situation and for which the tuning seems
    to be a black art.
 5. In an N node cluster, only 1/N of the dropped locked will actually
    contribute to solving the problem on average.

So all in all we are better off without it. This also makes merging
the lock_dlm module into GFS2 a bit easier.

Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;
</content>
</entry>
<entry>
<title>[GFS2] Remove unused counters</title>
<updated>2008-03-31T09:40:34Z</updated>
<author>
<name>Bob Peterson</name>
</author>
<published>2008-02-05T23:11:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9feb7c889f2a3b088a7f6583e609bd39997c0f47'/>
<id>urn:sha1:9feb7c889f2a3b088a7f6583e609bd39997c0f47</id>
<content type='text'>
This is kind of trivial in the greater scheme of things, but
this removes three counters that AFAICT are never used.

Signed-off-by: Bob Peterson &lt;rpeterso@redhat.com&gt;
Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;
</content>
</entry>
<entry>
<title>[GFS2] Remove lm.[ch] and distribute content</title>
<updated>2008-03-31T09:40:26Z</updated>
<author>
<name>Steven Whitehouse</name>
</author>
<published>2008-01-30T15:34:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=da755fdb414470d6dce3df12ad188de9131cf96c'/>
<id>urn:sha1:da755fdb414470d6dce3df12ad188de9131cf96c</id>
<content type='text'>
The functions in lm.c were just wrappers which were mostly
only used in one other file. By moving the functions to
the files where they are being used, they can be marked
static and also this will usually result in them being inlined
since they are often only used from one point in the code.

A couple of really trivial functions have been inlined by hand
into the function which called them as it makes the code clearer
to do that.

We also gain from one fewer function call in the glock lock and
unlock paths.

Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-nmw</title>
<updated>2008-01-25T16:39:18Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2008-01-25T16:39:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e07dd2ad305f6b29b47d713600aa8b722ef2a9f7'/>
<id>urn:sha1:e07dd2ad305f6b29b47d713600aa8b722ef2a9f7</id>
<content type='text'>
* git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-2.6-nmw: (56 commits)
  [GFS2] Allow journal recovery on read-only mount
  [GFS2] Lockup on error
  [GFS2] Fix page_mkwrite truncation race path
  [GFS2] Fix typo
  [GFS2] Fix write alloc required shortcut calculation
  [GFS2] gfs2_alloc_required performance
  [GFS2] Remove unneeded i_spin
  [GFS2] Reduce inode size by moving i_alloc out of line
  [GFS2] Fix assert in log code
  [GFS2] Fix problems relating to execution of files on GFS2
  [GFS2] Initialize extent_list earlier
  [GFS2] Allow page migration for writeback and ordered pages
  [GFS2] Remove unused variable
  [GFS2] Fix log block mapper
  [GFS2] Minor correction
  [GFS2] Eliminate the no longer needed sd_statfs_mutex
  [GFS2] Incremental patch to fix compiler warning
  [GFS2] Function meta_read optimization
  [GFS2] Only fetch the dinode once in block_map
  [GFS2] Reorganize function gfs2_glmutex_lock
  ...
</content>
</entry>
<entry>
<title>[GFS2] Don't periodically update the jindex</title>
<updated>2008-01-25T08:07:59Z</updated>
<author>
<name>Steven Whitehouse</name>
</author>
<published>2007-11-09T10:07:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e35b921185728850c5db3b5d5b356178f931a157'/>
<id>urn:sha1:e35b921185728850c5db3b5d5b356178f931a157</id>
<content type='text'>
We only care about the content of the jindex in two cases,
one is when we mount the fs and the other is when we need
to recover another journal. In both cases we have to update
the jindex anyway, so there is no point in updating it
periodically between times, so this removes it to simplify
gfs2_logd.

Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;
</content>
</entry>
<entry>
<title>[GFS2] Given device ID rather than s_id in "id" sysfs file</title>
<updated>2008-01-25T08:07:47Z</updated>
<author>
<name>Bob Peterson</name>
</author>
<published>2007-11-02T14:37:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c7227e46423a57b4df27a2d75b5869bd3ae654d0'/>
<id>urn:sha1:c7227e46423a57b4df27a2d75b5869bd3ae654d0</id>
<content type='text'>
This patch changes the /sys/fs/gfs2/&lt;s_id&gt;/id file to give the device
id "major:minor" rather than the s_id.  That enables gfs2_tool to
match devices properly (by id, not name) when locating the tuning files.

Signed-off-by: Bob Peterson &lt;rpeterso@redhat.com&gt;
Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;
</content>
</entry>
<entry>
<title>[GFS2] Remove "reclaim limit"</title>
<updated>2008-01-25T08:07:37Z</updated>
<author>
<name>Steven Whitehouse</name>
</author>
<published>2007-11-01T09:26:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c2932e03dbcfe7ea9052953dbd5f3157183c1e9b'/>
<id>urn:sha1:c2932e03dbcfe7ea9052953dbd5f3157183c1e9b</id>
<content type='text'>
This call to reclaim glocks is not needed, and in particular we don't want it
in the fast path for locking glocks. The limit was entirely arbitrary anyway
and we can't expect users to adjust things like this, the remaining code will
do the right thing on its own.

Signed-off-by: Steven Whitehouse &lt;swhiteho@redhat.com&gt;
</content>
</entry>
<entry>
<title>Kobject: convert fs/* from kobject_unregister() to kobject_put()</title>
<updated>2008-01-25T04:40:40Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
</author>
<published>2007-12-20T16:13:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=197b12d6796a3bca187f22a8978a33d51e2bcd79'/>
<id>urn:sha1:197b12d6796a3bca187f22a8978a33d51e2bcd79</id>
<content type='text'>
There is no need for kobject_unregister() anymore, thanks to Kay's
kobject cleanup changes, so replace all instances of it with
kobject_put().


Cc: Kay Sievers &lt;kay.sievers@vrfy.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
