linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Al Boldi <a1426z@gawab.com>
Cc: "Bryan J. Smith" <b.j.smith@ieee.org>,
	Joshua Baker-LePain <jlb17@duke.edu>, David Chinner <dgc@sgi.com>,
	Justin Piszcz <jpiszcz@lucidpixels.com>,
	Jon Collette <jon@etelos.com>,
	linux-ide-arrays@lists.math.uh.edu, linux-raid@vger.kernel.org,
	xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] VFS: data=ordered  (was: [Advocacy] Re: 3ware 9650 tips)
Date: Mon, 16 Jul 2007 13:02:54 -0600	[thread overview]
Message-ID: <20070716190254.GP13826@parisc-linux.org> (raw)
In-Reply-To: <200707162128.08397.a1426z@gawab.com>

On Mon, Jul 16, 2007 at 09:28:08PM +0300, Al Boldi wrote:
> Well, conceptually it sounds like a piece of cake, technically your guess is 
> as good as mine.  IIRC, akpm once mentioned something like this.

How much have you looked at the VFS?  There's nothing journalling-related
in the VFS right now.  ext3 and XFS share no common journalling code,
nor do I think that would be possible, due to the very different concepts
they have of journalling.

Here's a good hint:

$ find fs -type f |xargs grep -l journal_start
fs/ext3/acl.c
fs/ext3/inode.c
fs/ext3/ioctl.c
fs/ext3/namei.c
fs/ext3/resize.c
fs/ext3/super.c
fs/ext3/xattr.c
fs/ext4/acl.c
fs/ext4/extents.c
fs/ext4/inode.c
fs/ext4/ioctl.c
fs/ext4/namei.c
fs/ext4/resize.c
fs/ext4/super.c
fs/ext4/xattr.c
fs/jbd/journal.c
fs/jbd/transaction.c
fs/jbd2/journal.c
fs/jbd2/transaction.c
fs/ocfs2/journal.c
fs/ocfs2/super.c

JBD and JBD2 provide a journalling implementation that ext3, ext4 and
ocfs2 use.  Note that XFS doesn't, it has its own journalling code.

If you want XFS to support data=ordered, talk to the XFS folks.  Or
start picking through XFS yourself, of course -- you do have the source
code.

-- 
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2007-07-16 19:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LRH.0.999.0707131356520.25773@chaos.egr.duke.edu>
     [not found] ` <alpine.LRH.0.999.0707161142440.25773@chaos.egr.duke.edu>
     [not found]   ` <1184606132.4551.11.camel@portatux64.mobile.smithconcepts.com>
2007-07-16 17:40     ` [Advocacy] Re: 3ware 9650 tips Al Boldi
2007-07-16 17:48       ` Matthew Wilcox
2007-07-16 18:28         ` [RFC] VFS: data=ordered (was: [Advocacy] Re: 3ware 9650 tips) Al Boldi
2007-07-16 19:02           ` Matthew Wilcox [this message]
2007-07-16 18:38         ` [Advocacy] Re: 3ware 9650 tips Bryan J. Smith

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=20070716190254.GP13826@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=a1426z@gawab.com \
    --cc=b.j.smith@ieee.org \
    --cc=dgc@sgi.com \
    --cc=jlb17@duke.edu \
    --cc=jon@etelos.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ide-arrays@lists.math.uh.edu \
    --cc=linux-raid@vger.kernel.org \
    --cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).