public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: [git patches] ocfs2 updates
Date: Tue, 12 Dec 2006 10:16:37 -0800	[thread overview]
Message-ID: <20061212181637.GF6831@ca-server1.us.oracle.com> (raw)

Hi Linus,

A few more patches to push upstream before 2.6.20-rc1. This set includes:

* Some patches to make ocfs2 network timeout values user-adjustable. The
  values are set / read via the configfs interface and are validated against
  other nodes when they initiate a connection.

* A "local mount" patch which gives ocfs2 the ability to act as a local file
  system (no cluster configuration needed, no dlm locking, etc).

* Various cleanups - a documentation update, and a sync of ocfs2_fs.h
  between kernel and user tools.

Please pull from 'upstream-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/mfasheh/ocfs2.git upstream-linus

to receive the following updates:

 Documentation/filesystems/ocfs2.txt |    3 
 fs/ocfs2/cluster/nodemanager.c      |  192 +++++++++++++++++++++++++++++++++---
 fs/ocfs2/cluster/nodemanager.h      |   17 +++
 fs/ocfs2/cluster/tcp.c              |  152 ++++++++++++++++++++++++----
 fs/ocfs2/cluster/tcp.h              |    8 +
 fs/ocfs2/cluster/tcp_internal.h     |   15 +-
 fs/ocfs2/dlmglue.c                  |   79 +++++++++++---
 fs/ocfs2/heartbeat.c                |    9 +
 fs/ocfs2/inode.c                    |    3 
 fs/ocfs2/journal.c                  |   46 ++++++--
 fs/ocfs2/journal.h                  |    5 
 fs/ocfs2/mmap.c                     |    6 -
 fs/ocfs2/namei.c                    |    8 -
 fs/ocfs2/ocfs2.h                    |    5 
 fs/ocfs2/ocfs2_fs.h                 |   14 ++
 fs/ocfs2/super.c                    |   90 ++++++++++++----
 fs/ocfs2/vote.c                     |    3 
 17 files changed, 549 insertions(+), 106 deletions(-)

Andrew Beekhof:
      [patch 1/3] OCFS2 - Expose struct o2nm_cluster
      [patch 3/3] OCFS2 Configurable timeouts - Protocol changes

Jeff Mahoney:
      [patch 2/3] OCFS2 Configurable timeouts

Mark Fasheh:
      ocfs2: Synchronize feature incompat flags in ocfs2_fs.h

Sunil Mushran:
      ocfs2: local mounts

Tiger Yang:
      ocfs2: update mount option documentation


Thanks,
	--Mark

--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com

             reply	other threads:[~2006-12-12 18:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 18:16 Mark Fasheh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-12 19:34 [git patches] ocfs2 updates Mark Fasheh
2007-05-25 18:17 Mark Fasheh
2007-04-27 17:23 Mark Fasheh
2006-09-21 19:12 Mark Fasheh
2006-08-15 19:20 Mark Fasheh
2006-08-15 19:32 ` Greg KH
2006-06-30  0:05 Mark Fasheh
2006-03-24 23:40 Mark Fasheh
2006-03-06 22:36 Mark Fasheh
2006-03-01 23:10 Mark Fasheh
2006-03-01 23:37 ` Andrew Morton
2006-03-01 23:52   ` Mark Fasheh
2006-02-16 21:22 Mark Fasheh
2006-02-03 23:02 Mark Fasheh
2006-01-20  1:37 Mark Fasheh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061212181637.GF6831@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox