From: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org,
ryusuke-sG5X7nlA6pw@public.gmane.org,
Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
Subject: [PATCHv4 0/2] nilfs2: asynchronous sb update
Date: Fri, 25 Jun 2010 00:27:38 +0900 [thread overview]
Message-ID: <1277393260-19835-1-git-send-email-jir@unicus.jp> (raw)
Hi,
This is v4 patch series to update super block asynchronously.
First patch separates super block validity check from nilfs_commit_super,
and moved the function into callers.
Second patch introduces swapping code in nilfs_prepare_super.
Caller of the function must specify whether swapping super blocks or not
explicitly. To advance log pointer, the caller uses nilfs_set_log_cursor
to advance specified super block after calling nilfs_prepare_super.
changes from v3
- move swapping code to nilfs_prepare_super from nilfs_sync_super
- check last_cno of super blocks to advance protection period
- introduce nilfs_sb_need_swap function
changes from v2
- restore super block in nilfs_prepare_super
- introduce nilfs_set_error
* used in nilfs_error
- introduce nilfs_set_log_cursor instead of write_log_cursor
* instead of writing error, set log cursor to specified sb pointer
* used followed by nilfs_commit_super
- introduce ns_sbwcount
* swap super blocks based on the counter
* swap all most all the time, still asymmetric(9:7 ratio)
- delete ns_sbwtime[2]
* introduce ns_sbwtime instead of array of both super blocks
- synchronize super blocks when mount/remount
- abandon NILFS_SB_SET_FN
* only used in nilfs_set_error, so assign directly in the function
- misc style fix
- misc comment fix
changes from v1
- change macro name NILFS_SUPER_SET_FN -> NILFS_SB_SET_FN
* change inline function name as nilfs_sb_set_##name
- introduce enum for nilfs_commit_super and nilfs_sync_super
* NILFS_SB_COMMIT and NILFS_SB_COMMIT_ALL
* use flag instead of dupsb in nilfs_commit_super/sync_super
fs/nilfs2/nilfs.h | 12 +++
fs/nilfs2/segment.c | 10 ++-
fs/nilfs2/super.c | 182 ++++++++++++++++++++++++++++++++++---------------
fs/nilfs2/the_nilfs.c | 17 +++--
fs/nilfs2/the_nilfs.h | 17 ++---
5 files changed, 166 insertions(+), 72 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2010-06-24 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 15:27 Jiro SEKIBA [this message]
[not found] ` <1277393260-19835-1-git-send-email-jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
2010-06-24 15:27 ` [PATCHv4 1/2] nilfs2: introduce nilfs_prepare_super Jiro SEKIBA
2010-06-24 15:27 ` [PATCHv4 2/2] nilfs2: sync super blocks in turns Jiro SEKIBA
[not found] ` <1277393260-19835-3-git-send-email-jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
2010-06-25 9:06 ` Ryusuke Konishi
[not found] ` <20100625.180639.160014063.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-06-26 5:05 ` Jiro SEKIBA
[not found] ` <87zkyi1izo.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-06-26 7:10 ` CentOS 5 support for nilfs Martin, Nick
[not found] ` <A94BFDB17DC4E1478F7ACF6EBA3FD8234AE3F6E52D-7hT9n0F4+5en5JXSkZkeBYboaULrDjGDrOgnGio5az8@public.gmane.org>
2010-06-26 15:24 ` Ryusuke Konishi
[not found] ` <A94BFDB17DC4E1478F7ACF6EBA3FD8234AE3F6E661@p3saturn.p3corpnet.pivot3.com>
[not found] ` <A94BFDB17DC4E1478F7ACF6EBA3FD8234AE3F6E661-7hT9n0F4+5en5JXSkZkeBYboaULrDjGDrOgnGio5az8@public.gmane.org>
2010-06-29 5:59 ` Ryusuke Konishi
2010-06-26 14:51 ` [PATCHv4 2/2] nilfs2: sync super blocks in turns Ryusuke Konishi
[not found] ` <20100626.235108.163664714.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-06-27 3:22 ` Jiro SEKIBA
[not found] ` <87sk49dur6.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-06-28 2:35 ` Ryusuke Konishi
2010-06-24 16:56 ` [PATCHv4 0/2] nilfs2: asynchronous sb update Ryusuke Konishi
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=1277393260-19835-1-git-send-email-jir@unicus.jp \
--to=jir-hfpbi5wx9j54eiagz67ipq@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ryusuke-sG5X7nlA6pw@public.gmane.org \
/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