From: Nick Piggin <npiggin@suse.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Announce: new-aops-1 for 2.6.21-rc3
Date: Thu, 15 Mar 2007 17:17:04 +0100 [thread overview]
Message-ID: <20070315161704.GH8321@wotan.suse.de> (raw)
OK, I've gone through and fixed several bugs until the thing actually
survives fsx-linux for both ext2 and ext3 ordered and writeback (both
when using the new aops, and the legacy prepare_write path). Actually
ext3 sometimes breaks, but it does in unpatched kernels anyway.
At 15 patches (including the initial buffered write deadlock fixes),
it is too much to keep posting -- not much has fundamentally changed,
so I'll just post occasionally if we make big changes. The quilt
format is probably easier for someone wishing to work on it anyway.
http://www.kernel.org/pub/linux/kernel/people/npiggin/patches/new-aops/
(excludes the OCFS2 patch that Mark sent, in anticipation of an update)
It would be really nice if filesystem developers could take a look
at the new interfaces some time, because otherwise they might get stuck
with it :) So I'm cc'ing a few filesystems that come to mind, that I
haven't heard anything from.
Thanks,
Nick
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <npiggin@suse.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Announce: new-aops-1 for 2.6.21-rc3
Date: Thu, 15 Mar 2007 17:17:04 +0100 [thread overview]
Message-ID: <20070315161704.GH8321@wotan.suse.de> (raw)
Message-ID: <20070315161704.eVufpvkszT00KGjoEdNpzAibJWUUbldzEI1dA7O--sk@z> (raw)
OK, I've gone through and fixed several bugs until the thing actually
survives fsx-linux for both ext2 and ext3 ordered and writeback (both
when using the new aops, and the legacy prepare_write path). Actually
ext3 sometimes breaks, but it does in unpatched kernels anyway.
At 15 patches (including the initial buffered write deadlock fixes),
it is too much to keep posting -- not much has fundamentally changed,
so I'll just post occasionally if we make big changes. The quilt
format is probably easier for someone wishing to work on it anyway.
http://www.kernel.org/pub/linux/kernel/people/npiggin/patches/new-aops/
(excludes the OCFS2 patch that Mark sent, in anticipation of an update)
It would be really nice if filesystem developers could take a look
at the new interfaces some time, because otherwise they might get stuck
with it :) So I'm cc'ing a few filesystems that come to mind, that I
haven't heard anything from.
Thanks,
Nick
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <npiggin@suse.de>
To: Linux Filesystems <linux-fsdevel@vger.kernel.org>,
Mark Fasheh <mark.fasheh@oracle.com>
Cc: reiserfs-list@namesys.com, linux-ext4@vger.kernel.org,
xfs@oss.sgi.com, nfs@lists.sourceforge.net,
cluster-devel@redhat.com, jfs-discussion@lists.sourceforge.net
Subject: Announce: new-aops-1 for 2.6.21-rc3
Date: Thu, 15 Mar 2007 17:17:04 +0100 [thread overview]
Message-ID: <20070315161704.GH8321@wotan.suse.de> (raw)
OK, I've gone through and fixed several bugs until the thing actually
survives fsx-linux for both ext2 and ext3 ordered and writeback (both
when using the new aops, and the legacy prepare_write path). Actually
ext3 sometimes breaks, but it does in unpatched kernels anyway.
At 15 patches (including the initial buffered write deadlock fixes),
it is too much to keep posting -- not much has fundamentally changed,
so I'll just post occasionally if we make big changes. The quilt
format is probably easier for someone wishing to work on it anyway.
http://www.kernel.org/pub/linux/kernel/people/npiggin/patches/new-aops/
(excludes the OCFS2 patch that Mark sent, in anticipation of an update)
It would be really nice if filesystem developers could take a look
at the new interfaces some time, because otherwise they might get stuck
with it :) So I'm cc'ing a few filesystems that come to mind, that I
haven't heard anything from.
Thanks,
Nick
next reply other threads:[~2007-03-15 16:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 16:17 Nick Piggin [this message]
2007-03-15 16:17 ` Announce: new-aops-1 for 2.6.21-rc3 Nick Piggin
2007-03-15 16:17 ` [Cluster-devel] " Nick Piggin
2007-03-15 19:32 ` [Cluster-devel] " Joel Becker
2007-03-15 19:32 ` Joel Becker
2007-03-15 19:32 ` Joel Becker
2007-03-15 19:57 ` [Cluster-devel] " Nick Piggin
2007-03-15 19:57 ` Nick Piggin
2007-03-15 19:53 ` [Cluster-devel] " Mark Fasheh
2007-03-15 19:53 ` Mark Fasheh
2007-03-15 19:53 ` Mark Fasheh
2007-03-15 19:57 ` [Cluster-devel] " Nick Piggin
2007-03-15 19:57 ` Nick Piggin
2007-03-15 19:57 ` Nick Piggin
2007-03-15 21:08 ` [Cluster-devel] " Mark Fasheh
2007-03-15 21:08 ` Mark Fasheh
2007-03-15 21:08 ` Mark Fasheh
2007-03-15 23:47 ` [Cluster-devel] " Mark Fasheh
2007-03-15 23:47 ` Mark Fasheh
2007-03-15 23:47 ` Mark Fasheh
2007-03-20 5:36 ` [Cluster-devel] " Nick Piggin
2007-03-20 5:36 ` Nick Piggin
2007-04-01 5:42 ` Nick Piggin
2007-04-02 2:14 ` Nick Piggin
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=20070315161704.GH8321@wotan.suse.de \
--to=npiggin@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.