Linux NILFS development
 help / color / mirror / Atom feed
From: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org,
	Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>,
	Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
Subject: [PATCH 0/2] nilfs2: asynchronous super block updates
Date: Wed,  9 Jun 2010 07:15:56 +0900	[thread overview]
Message-ID: <1276035358-24284-1-git-send-email-jir@unicus.jp> (raw)

Hi,

This is revised 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 nilfs_write_log_cursor to advance log cursor
for one of super blocks.  This patch also define a macro that generates
inline function to update information both super blocks for convenience.


 fs/nilfs2/nilfs.h     |    2 +
 fs/nilfs2/segment.c   |    8 +--
 fs/nilfs2/super.c     |  144 ++++++++++++++++++++++++++++++++++---------------
 fs/nilfs2/the_nilfs.c |   11 +++-
 fs/nilfs2/the_nilfs.h |   23 +++++---
 5 files changed, 128 insertions(+), 60 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

             reply	other threads:[~2010-06-08 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 22:15 Jiro SEKIBA [this message]
     [not found] ` <1276035358-24284-1-git-send-email-jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
2010-06-08 22:15   ` [PATCH 1/2] nilfs2: introduce nilfs_prepare_super Jiro SEKIBA
2010-06-08 22:15   ` [PATCH 2/2] nilfs2: sync super blocks in turns Jiro SEKIBA
2010-06-09  1:36   ` [PATCH 0/2] nilfs2: asynchronous super block updates Ryusuke Konishi
  -- strict thread matches above, loose matches on Subject: below --
2010-06-05 22:19 Jiro SEKIBA

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=1276035358-24284-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