From: Paul Jackson <pj@sgi.com>
To: Paul Jackson <pj@sgi.com>
Cc: jmorris@redhat.com, mark.fasheh@oracle.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
ocfs2-devel@oss.oracle.com, torvalds@osdl.org, akpm@osdl.org,
wim.coekaerts@oracle.com, lmb@suse.de
Subject: Re: [RFC] [PATCH] OCFS2
Date: Thu, 23 Jun 2005 20:29:06 -0700 [thread overview]
Message-ID: <20050623202906.39c8ec8a.pj@sgi.com> (raw)
In-Reply-To: <20050623200524.298a6ab4.pj@sgi.com>
A couple more random questions:
1) How does this lock manager relate to the Red Hat lock manager,
the dlm-* patches?
Note as an aside that dlm-* has 23 patches for a total of 14
thousand lines, or about 600 lines per patch. This is rather
different than burying a lock manager into a 45 thousand line
new file system patch ;)
2) Would a diffstat be a useful addition to this patch?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2005-06-24 3:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 22:33 [RFC] [PATCH] OCFS2 Mark Fasheh
2005-05-18 23:35 ` Hans Reiser
2005-05-18 23:40 ` Adrian Bunk
2005-05-19 1:26 ` [Ocfs2-devel] " Manish Singh
2005-05-19 9:45 ` Adrian Bunk
2005-05-19 10:24 ` 2.4 kernel threads linux
2005-05-19 10:39 ` Arjan van de Ven
2005-05-19 16:19 ` Jesse Barnes
2005-05-19 2:30 ` [RFC] [PATCH] OCFS2 Kyle Moffett
2005-05-19 4:30 ` Mark Fasheh
2005-05-19 6:30 ` Daniel Phillips
2005-05-19 6:54 ` Mark Fasheh
2005-05-19 16:23 ` Daniel Phillips
2005-05-19 10:26 ` Jeff Garzik
2005-05-19 15:20 ` Lee Revell
2005-05-19 15:25 ` Jeff Garzik
2005-06-23 18:03 ` James Morris
2005-06-23 18:29 ` Mark Fasheh
2005-06-24 3:05 ` Paul Jackson
2005-06-24 3:29 ` Paul Jackson [this message]
2005-06-24 3:59 ` Mark Fasheh
2005-06-24 4:17 ` Paul Jackson
-- strict thread matches above, loose matches on Subject: below --
2005-06-21 21:14 Steve French
2005-06-21 22:03 ` Mark Fasheh
2005-06-21 22:43 ` Steve French
2005-06-22 0:04 ` 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=20050623202906.39c8ec8a.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=jmorris@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=torvalds@osdl.org \
--cc=wim.coekaerts@oracle.com \
/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