Hi, this is the latest set of gfs patches, it includes some minor munging
since the previous set. Andrew, could this be added to -mm? there's not
much in the way of pending changes.
http://redhat.com/~teigland/gfs2/20050901/gfs2-full.patch
http://redhat.com/~teigland/gfs2/20050901/broken-out/
There are a variety of mount options, tunable parameters, internal
statistics, and methods of online file system manipulation.
Signed-off-by: Ken Preslan [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/ioctl.c | 1485
The lock_dlm module uses the DLM in linux/drivers/dlm/ for inter-node
locking.
Signed-off-by: Ken Preslan [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/locking/dlm/Makefile |3
fs/gfs2/locking/dlm/lock.c | 533
Code that deals with quotas.
Signed-off-by: Ken Preslan [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/lvb.c | 61 ++
fs/gfs2/lvb.h | 28 +
fs/gfs2/quota.c | 1209
fs/gfs2/quota.h | 34 +
4 files
A per-node on-disk log is used for recovery.
Signed-off-by: Ken Preslan [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/log.c | 670 +
fs/gfs2/log.h | 68 +
fs/gfs2/recovery.c | 561
Code that handles extended attributes and ACL's.
Signed-off-by: Ken Preslan [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/acl.c | 313 ++
fs/gfs2/acl.h | 37 +
fs/gfs2/eaops.c | 179 ++
fs/gfs2/eaops.h | 30 +
fs/gfs2/eattr.c | 1621
Add gfs to the build system and gfs2.txt to Documentation.
Signed-off-by: Ken Preslan [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
Documentation/filesystems/gfs2.txt | 194 +
fs/Kconfig | 15 ++
fs/Makefile
The lock_nolock module does no inter-node locking and allows gfs to be
used as a local file system.
Signed-off-by: Ken Preslan [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/locking/nolock/Makefile |3
fs/gfs2/locking/nolock/main.c | 267
The lock_harness module allows a gfs file system to connect to a given
lock module.
Signed-off-by: Ken Preslan [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/locking/harness/Makefile |3
fs/gfs2/locking/harness/lm_interface.h | 286
Central header files that are widely used.
Signed-off-by: Ken Preslan [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/gfs2.h | 77 +++
fs/gfs2/incore.h| 691 +++
include/linux/gfs2_ioctl.h | 30 +
include
Code that manages block allocation.
Signed-off-by: Ken Preslan [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/bits.c | 179 +++
fs/gfs2/bits.h | 28 +
fs/gfs2/rgrp.c | 1374 +
fs/gfs2/rgrp.h | 62
Code that handles directory operations.
Signed-off-by: Ken Preslan [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
---
fs/gfs2/dir.c | 2158 ++
fs/gfs2/dir.h | 51 +
2 files changed, 2209 insertions(+)
--- a/fs/gfs2
On Thu, Sep 01, 2005 at 04:19:34PM +0200, Arjan van de Ven wrote:
+/* Endian functions */
e again why??
Why is this a compiletime hack?
Either you care about either-endian on disk, at which point it has to be
a runtime thing, or you make the on disk layout fixed endian, at which
On Thu, Sep 01, 2005 at 01:21:04PM -0700, Andrew Morton wrote:
Alan Cox [EMAIL PROTECTED] wrote:
- Why GFS is better than OCFS2, or has functionality which OCFS2 cannot
possibly gain (or vice versa)
- Relative merits of the two offerings
You missed the important one - people
On Sat, Sep 03, 2005 at 08:14:00AM +0200, Arjan van de Ven wrote:
On Sat, 2005-09-03 at 13:18 +0800, David Teigland wrote:
On Thu, Sep 01, 2005 at 01:21:04PM -0700, Andrew Morton wrote:
Alan Cox [EMAIL PROTECTED] wrote:
- Why GFS is better than OCFS2, or has functionality which OCFS2
On Mon, Sep 05, 2005 at 01:54:08AM -0700, Andrew Morton wrote:
David Teigland [EMAIL PROTECTED] wrote:
We export our full dlm API through read/write/poll on a misc device.
inotify did that for a while, but we ended up going with a straight syscall
interface.
How fat is the dlm
On Mon, Sep 05, 2005 at 02:19:48AM -0700, Andrew Morton wrote:
David Teigland [EMAIL PROTECTED] wrote:
Four functions:
create_lockspace()
release_lockspace()
lock()
unlock()
Neat. I'd be inclined to make them syscalls then. I don't suppose anyone
is likely to object if we
On Thu, Sep 01, 2005 at 01:35:23PM +0200, Arjan van de Ven wrote:
+static inline void glock_put(struct gfs2_glock *gl)
+{
+ if (atomic_read(gl-gl_count) == 1)
+ gfs2_glock_schedule_for_reclaim(gl);
+ gfs2_assert(gl-gl_sbd, atomic_read(gl-gl_count) 0,);
+
On Wed, Dec 06, 2006 at 12:34:20AM -0500, J. Bruce Fields wrote:
+int gdlm_plock_callback(struct plock_op *op)
+{
+ struct file *file;
+ struct file_lock *fl;
+ int rv;
+
+ spin_lock(ops_lock);
+ if (!list_empty(op-list)) {
+ printk(KERN_INFO plock op on
On Wed, Dec 06, 2006 at 02:57:22PM -0500, J. Bruce Fields wrote:
On Wed, Dec 06, 2006 at 09:49:51AM -0600, David Teigland wrote:
The gfs side looks fine to me. Did you forget to call fl_notify from
gdlm_plock_callback() or am I missing something?
Yes, looks like we missed something
On Wed, Dec 06, 2006 at 05:00:29PM -0500, J. Bruce Fields wrote:
On Wed, Dec 06, 2006 at 03:42:31PM -0600, David Teigland wrote:
Oh yeah, that's painful, I knew it sounded too easy.
Yeah. Well, we could try to teach GFS2 to reliably cancel posix locks.
I think that may turn out
On Tue, Feb 20, 2007 at 10:46:51AM -0500, Robert Rappaport wrote:
Thank you both for your helpful replies. In particular, the addition
of the calls to file system specific functions in routines,
fcntl_setlease() and break_lease(), as well as the modifications to
the file_operations and
On Tue, Feb 20, 2007 at 03:51:54PM -0500, [EMAIL PROTECTED] wrote:
On Tue, Feb 20, 2007 at 10:46:51AM -0500, Robert Rappaport wrote:
We did an experimental distributed lease implementation in gfs(1) a while
ago. It worked, but was so extremely expensive that there was no point in
On Thu, Feb 22, 2007 at 04:58:28PM -0500, J. Bruce Fields wrote:
I'm also curious--exposing my total ignorance of the dlm--why taking
such a lock would always be so expensive, or would always be required on
open. Surely the typical case should be one where there's no conflict
and never has
24 matches
Mail list logo
