All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Theodore Ts'o <tytso@mit.edu>
Cc: jack@suse.cz, linux-kernel@vger.kernel.org,
	linux-ext4@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: What happened to data=guarded? (was: ext3: Update Kconfig description of EXT3_DEFAULTS_TO_ORDERED)
Date: Tue, 11 Aug 2009 15:35:36 +0200	[thread overview]
Message-ID: <200908111535.37927.elendil@planet.nl> (raw)
In-Reply-To: <1249934623-15939-1-git-send-email-tytso@mit.edu>

> The old description for this configuration option was perhaps not
> completely balanced in terms of describing the tradeoffs of using a
> default of data=writeback vs. data=ordered.

Somewhat unrelated, but what happened to the data=guarded patches Chris 
Mason proposed back in April?

Cheers,
FJP

  parent reply	other threads:[~2009-08-11 13:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 20:03 [PATCH, RFC] ext3: Update Kconfig description of EXT3_DEFAULTS_TO_ORDERED Theodore Ts'o
2009-08-10 20:28 ` Jan Kara
2009-08-10 20:55 ` Ric Wheeler
2009-08-11  3:49 ` Al Boldi
2009-08-11  9:33   ` Jan Kara
2009-08-11 11:41     ` Al Boldi
2009-08-11 13:35 ` Frans Pop [this message]
2009-08-11 13:37   ` What happened to data=guarded? (was: ext3: Update Kconfig description of EXT3_DEFAULTS_TO_ORDERED) Chris Mason
2009-08-11 14:54     ` What happened to data=guarded? Frans Pop
2009-08-11 15:29       ` Andi Kleen
2009-08-11 15:34         ` Jan Kara
2009-08-11 18:04           ` Eric Sandeen
2009-08-11 18:57         ` Theodore Tso
2009-08-10 16:42           ` Pavel Machek
2009-08-10 16:42             ` Pavel Machek
2009-08-11 22:00             ` Bernd Eckenfels
2009-08-12 20:37             ` Jan Kara
2009-08-11 19:09           ` Andi Kleen
2009-08-11 19:09             ` Andi Kleen

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=200908111535.37927.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=chris.mason@oracle.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.