From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/9] Log and transaction cleanups, factoring and bug fixes V2
Date: Mon, 15 Mar 2010 13:34:57 +1100 [thread overview]
Message-ID: <1268620506-10799-1-git-send-email-david@fromorbit.com> (raw)
The following series is preparation for delayed logging patches. The cleanups
and factoring patches are mainly to make it simple to introduce the delayed
logging patches, especially as these changes really have nothing to do with
delayed logging. The cleanups and factoring patches should be no-ops from a
functionality point of view.
A couple of the patches are fixes for bugs that I've found as I've been working
through delayed logging prototypes.
Patches 8 (reservation bug fix) and 9 (new cleanup) of the series still
require review.
Version 2:
- drop log vector changes from the series
- fix bogus assert in xfs_trans_committed() changes
- Added Christoph's _xfs_trans_commit() cleanup patch
- Added further cleanup of the xfs_trans_committed() code as suggested by
Christoph.
These changes are also available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfs.git trans-cleanup
Christoph Hellwig (1):
xfs: clean up xfs_trans_commit logic even more
Dave Chinner (8):
xfs: factor log item initialisation
xfs: Add inode pin counts to traces
xfs: remove stale parameter from ->iop_unpin method
xfs: fix reservation release commit flag in xfs_bmap_add_attrfork()
xfs: split out iclog writing from xfs_trans_commit()
xfs: update and factor xfs_trans_committed()
xfs: Clean up xfs_trans_committed code after factoring
xfs: log ticket reservation underestimates the number of iclogs
fs/xfs/linux-2.6/xfs_trace.h | 9 +-
fs/xfs/quota/xfs_dquot_item.c | 28 +-
fs/xfs/xfs_bmap.c | 2 +-
fs/xfs/xfs_buf_item.c | 55 ++--
fs/xfs/xfs_extfree_item.c | 18 +-
fs/xfs/xfs_inode.c | 2 +
fs/xfs/xfs_inode_item.c | 21 +-
fs/xfs/xfs_log.c | 68 +++-
fs/xfs/xfs_log.h | 7 +
fs/xfs/xfs_trans.c | 760 +++++++++++++++++++----------------------
fs/xfs/xfs_trans.h | 5 +-
fs/xfs/xfs_trans_buf.c | 3 +-
12 files changed, 481 insertions(+), 497 deletions(-)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-03-15 2:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 2:34 Dave Chinner [this message]
2010-03-15 2:34 ` [PATCH 1/9] xfs: factor log item initialisation Dave Chinner
2010-03-15 2:34 ` [PATCH 2/9] xfs: Add inode pin counts to traces Dave Chinner
2010-03-15 2:35 ` [PATCH 3/9] xfs: remove stale parameter from ->iop_unpin method Dave Chinner
2010-03-15 2:35 ` [PATCH 4/9] xfs: fix reservation release commit flag in xfs_bmap_add_attrfork() Dave Chinner
2010-03-15 2:35 ` [PATCH 5/9] xfs: split out iclog writing from xfs_trans_commit() Dave Chinner
2010-03-15 2:35 ` [PATCH 6/9] xfs: clean up xfs_trans_commit logic even more Dave Chinner
2010-03-15 2:35 ` [PATCH 7/9] xfs: update and factor xfs_trans_committed() Dave Chinner
2010-03-15 2:35 ` [PATCH 8/9] xfs: Clean up xfs_trans_committed code after factoring Dave Chinner
2010-03-15 15:20 ` Christoph Hellwig
2010-03-15 2:35 ` [PATCH 9/9] xfs: log ticket reservation underestimates the number of iclogs Dave Chinner
2010-03-15 15:41 ` Christoph Hellwig
2010-03-15 15:44 ` Christoph Hellwig
2010-03-16 1:51 ` Dave Chinner
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=1268620506-10799-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--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