mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: kosaki.motohiro@jp.fujitsu.com, Jan Kara <jack@suse.cz>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Theodore Ts'o" <tytso@mit.edu>,
	Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>,
	Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH RFC] ext3 data=guarded v5
Date: Wed, 29 Apr 2009 11:12:18 +0900 (JST)	[thread overview]
Message-ID: <20090429110828.4B08.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <1240941840.15136.44.camel@think.oraclecorp.com>

Hi 

> Hello everyone,
> 
> I've rediffed the ext3 data=guarded code against Linus' current git
> tree, and worked in most of Jan's suggestions:

I'm not fs expert and I can't review it technically. but please don't
use the name of "guarded". this word implies strong protection. 

I think end-user can misunderstand this mode make slowness and strong protect
much than "mode=journal".




  parent reply	other threads:[~2009-04-29  2:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 18:04 Chris Mason
2009-04-28 18:33 ` Mike Galbraith
2009-04-28 18:54   ` Chris Mason
2009-04-29  2:12 ` KOSAKI Motohiro [this message]
2009-04-29  8:56 ` Jan Kara
2009-04-29 14:08   ` Chris Mason
2009-04-29 14:43     ` Chris Mason
2009-04-29 19:47       ` Andreas Dilger
2009-04-29 19:15     ` Jan Kara
2009-04-29 19:41       ` Chris Mason
2009-04-29 20:04         ` Jan Kara
2009-04-29 20:37           ` Chris Mason
2009-04-30 11:38             ` Jan Kara
2009-04-29 21:53         ` Theodore Tso
2009-04-29 19:51 ` [PATCH RFC] ext3 data=guarded v6 Chris Mason
2009-04-29 20:21   ` Jan Kara
2009-04-29 20:53   ` [PATCH RFC] ext3 data=guarded v7 Chris Mason
2009-04-30 11:52     ` Jan Kara
2009-04-30 13:17       ` Chris Mason

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=20090429110828.4B08.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --cc=efault@gmx.de \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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
all inboxes | Powered by JetHome®