linux.git/fs/dlm/debug_fs.c, branch v2.6.22

[PATCH] mark struct file_operations const 6

2007-02-12T17:48:45+00:00

Many struct file_operations in the kernel can be "const".  Marking them const
moves these to the .rodata section, which avoids false sharing with potential
dirty data.  In addition it'll catch accidental writes at compile time to
these shared resources.

Signed-off-by: Arjan van de Ven 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[GFS2] inode_diet: Replace inode.u.generic_ip with inode.i_private (gfs)

2006-09-28T12:32:24+00:00

The following patches reduce the size of the VFS inode structure by 28 bytes
on a UP x86.  (It would be more on an x86_64 system).  This is a 10% reduction
in the inode size on a UP kernel that is configured in a production mode
(i.e., with no spinlock or other debugging functions enabled; if you want to
save memory taken up by in-core inodes, the first thing you should do is
disable the debugging options; they are responsible for a huge amount of bloat
in the VFS inode structure).

This patch:

The filesystem or device-specific pointer in the inode is inside a union,
which is pretty pointless given that all 30+ users of this field have been
using the void pointer.  Get rid of the union and rename it to i_private, with
a comment to explain who is allowed to use the void pointer.  This is just a
cleanup, but it allows us to reuse the union 'u' for something something where
the union will actually be used.

Signed-off-by: "Theodore Ts'o" 
Cc: Steven Whitehouse 
Signed-off-by: Andrew Morton

[DLM] break from snprintf loop

2006-08-09T13:46:04+00:00

When the debug buffer has filled up, break from the loop and return the
correct number of bytes that have been written.

Signed-off-by: David Teigland 
Signed-off-by: Steven Whitehouse

[DLM] fix i_private

2006-07-26T19:31:15+00:00

> I think you must have an old version of the base kernel as well?
> i_private no longer exists in struct inode, so you'll have to use
> something else,

I have that patch in my stack but didn't send it; for some reason I
thought it was already changed in your git tree.

Signed-off-by: David Teigland 
Signed-off-by: Steven Whitehouse

[DLM] fix broken patches

2006-07-26T18:42:05+00:00

On Wed, Jul 26, 2006 at 10:47:14AM +0100, Steven Whitehouse wrote:
> Hi,
>
> I've applied all the patches you sent, but they don't build:

Argh, sorry about that... when I fixed these a long time ago they somehow
never got included in the quilt patches.  I mistakenly assumed the quilt
patches matched the source I had in front of me.

Signed-off-by: David Teigland 
Signed-off-by: Steven Whitehouse

[DLM] more info through debugfs

2006-07-26T12:41:37+00:00

Display more information from debugfs, particularly locks waiting for
a master lookup or operations waiting for a remote reply.

Signed-off-by: David Teigland 
Signed-off-by: Steven Whitehouse

[DLM] Remove range locks from the DLM

2006-02-23T09:56:38+00:00

This patch removes support for range locking from the DLM

Signed-off-by: David Teigland 
Signed-off-by: Steven Whitehouse

[DLM] Update DLM to the latest patch level

2006-01-20T08:47:07+00:00

Signed-off-by: David Teigland 
Signed-off-by: Steve Whitehouse

[DLM] The core of the DLM for GFS2/CLVM

2006-01-18T09:30:29+00:00

This is the core of the distributed lock manager which is required
to use GFS2 as a cluster filesystem. It is also used by CLVM and
can be used as a standalone lock manager independantly of either
of these two projects.

It implements VAX-style locking modes.

Signed-off-by: David Teigland 
Signed-off-by: Steve Whitehouse