From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/10] XFS: clean up sync code
Date: Sat, 13 Sep 2008 23:57:00 +1000 [thread overview]
Message-ID: <1221314230-28618-1-git-send-email-david@fromorbit.com> (raw)
xfs_sync and xfs_syncsub are multiplexed interfaces that
shares relatively little code between callers. because it is
a multiplexed interface, it's hard to tell what is executed
in each context it is called.
Factor out the sync code and explicitly call the sync functions
needed rather than the multiplexed interfaces. Once this is
done, we can remove xfs_syncsub and xfs_sync altogether.
next reply other threads:[~2008-09-13 13:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 13:57 Dave Chinner [this message]
2008-09-13 13:57 ` [PATCH 01/10] XFS: split out two helpers from xfs_syncsub Dave Chinner
2008-09-13 16:53 ` Josef 'Jeff' Sipek
2008-09-13 20:34 ` Dave Chinner
2008-09-13 13:57 ` [PATCH 02/10] XFS: Use struct inodes instead of vnodes to kill vn_grab Dave Chinner
2008-09-13 13:57 ` [PATCH 03/10] XFS: use xfs_sync_inodes rather than xfs_syncsub Dave Chinner
2008-09-13 13:57 ` [PATCH 04/10] XFS: kill xfs_syncsub Dave Chinner
2008-09-13 13:57 ` [PATCH 05/10] XFS: xfssyncd: don't call xfs_sync Dave Chinner
2008-09-13 16:58 ` Josef 'Jeff' Sipek
2008-09-13 20:35 ` Dave Chinner
2008-09-14 13:23 ` Christoph Hellwig
2008-09-13 13:57 ` [PATCH 06/10] XFS: make SYNC_ATTR no longer use xfs_sync Dave Chinner
2008-09-13 13:57 ` [PATCH 07/10] XFS: make SYNC_DELWRI no longer use xfs_sync V2 Dave Chinner
2008-09-13 13:57 ` [PATCH 08/10] XFS: Kill SYNC_CLOSE Dave Chinner
2008-09-13 13:57 ` [PATCH 09/10] XFS: Kill xfs_sync() Dave Chinner
2008-09-13 13:57 ` [PATCH 10/10] XFS: Move remaining quiesce code Dave Chinner
2008-09-14 13:24 ` [PATCH 0/10] XFS: clean up sync code Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2008-10-07 21:43 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=1221314230-28618-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