From: Chris Mason <chris.mason@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Theodore Tso <tytso@mit.edu>, Dave Chinner <david@fromorbit.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jens Axboe <axboe@kernel.dk>, dave b <db.pub.mail@gmail.com>,
Sanjoy Mahajan <sanjoy@olin.edu>, Jesper Juhl <jj@chaosbits.net>,
Ingo Molnar <mingo@elte.hu>, Pekka Enberg <penberg@kernel.org>,
Aidar Kultayev <the.aidar@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Nick Piggin <npiggin@suse.de>,
Arjan van de Ven <arjan@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Corrado Zoccolo <czoccolo@gmail.com>,
Shaohua Li <shaohua.li@intel.com>,
Steven Barrett <damentz@gmail.com>
Subject: Re: 2.6.36 io bring the system to its knees
Date: Wed, 10 Nov 2010 10:00:36 -0500 [thread overview]
Message-ID: <1289401148-sup-3632@think> (raw)
In-Reply-To: <20101110145712.GB22073@infradead.org>
Excerpts from Christoph Hellwig's message of 2010-11-10 09:57:12 -0500:
> On Wed, Nov 10, 2010 at 09:33:29AM -0500, Theodore Tso wrote:
> > The chance that this occurs using data=writeback in ext4 is much less, BTW, because with delayed allocation we delay updating the inode until right before we write the block. I have a plan for changing things so that we write the data blocks *first* and then update the metadata blocks second, which will mean that ext4 data=ordered will go away entirely, and we'll get both the safety and as well as avoiding the forced data page writeouts during journal commits.
>
> That's the scheme used by XFS and btrfs in one form or another. Chris
> also had a patch to implement it for ext3, which unfortunately fell
> under the floor.
It probably still applies, but by the time I had it stable I realized
that ext4 was really a better place to fix this stuff. ext3 is what it
is (good and bad), and a big change like my data=guarded code probably
isn't the best way to help.
-chris
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-10 15:03 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimt7wzR9RwGWbvhiOmot_zzayfCfSh_-v6yvuAP@mail.gmail.com>
[not found] ` <AANLkTikRKVBzO=ruy=JDmBF28NiUdJmAqb4-1VhK0QBX@mail.gmail.com>
[not found] ` <AANLkTinzJ9a+9w7G5X0uZpX2o-L8E6XW98VFKoF1R_-S@mail.gmail.com>
2010-10-28 6:09 ` 2.6.36 io bring the system to its knees Aidar Kultayev
2010-10-28 6:32 ` Pekka Enberg
2010-10-28 9:00 ` Ingo Molnar
2010-10-28 9:34 ` Pekka Enberg
2010-10-28 11:16 ` Pekka Enberg
2010-10-28 11:33 ` Aidar Kultayev
2010-10-28 11:48 ` Pekka Enberg
2010-10-28 12:18 ` Aidar Kultayev
2010-10-28 13:46 ` Christoph Hellwig
2010-10-28 13:54 ` Ingo Molnar
2010-10-28 13:30 ` Ingo Molnar
2010-10-28 13:47 ` Christoph Hellwig
2010-10-28 13:50 ` Ingo Molnar
2010-10-28 17:01 ` Chris Mason
2010-10-28 17:57 ` Pekka Enberg
2010-10-29 14:52 ` Ted Ts'o
2010-10-29 15:33 ` Aidar Kultayev
2010-10-30 9:14 ` Ingo Molnar
2010-10-30 13:02 ` Aidar Kultayev
2010-10-30 19:06 ` Chris Mason
2010-10-31 2:31 ` Ted Ts'o
2010-10-31 17:49 ` Corrado Zoccolo
2010-11-02 3:10 ` Shaohua Li
2010-11-02 11:47 ` Sanjoy Mahajan
2010-11-02 13:12 ` Chris Mason
2010-11-04 16:05 ` Sanjoy Mahajan
2010-11-04 23:35 ` Steven Barrett
2010-11-04 23:44 ` Jesper Juhl
2010-11-04 23:48 ` Jesper Juhl
2010-11-05 1:43 ` Dave Chinner
2010-11-05 12:48 ` Sanjoy Mahajan
2010-11-06 14:10 ` dave b
2010-11-06 15:12 ` Dave Chinner
2010-11-07 6:06 ` dave b
2010-11-07 12:08 ` Jens Axboe
2010-11-07 15:50 ` Linus Torvalds
2010-11-10 1:32 ` Dave Chinner
2010-11-10 2:01 ` dave b
2010-11-10 8:08 ` Evgeniy Ivanov
2010-11-10 8:24 ` Dave Chinner
2010-11-10 14:22 ` Pavel Machek
2010-11-10 14:20 ` Pavel Machek
2010-11-10 14:27 ` Ingo Molnar
2010-11-10 14:55 ` Christoph Hellwig
2010-11-10 19:09 ` Pavel Machek
2010-11-10 14:33 ` Theodore Tso
2010-11-10 14:57 ` Christoph Hellwig
2010-11-10 15:00 ` Chris Mason [this message]
2010-11-10 23:36 ` Dave Chinner
2010-11-10 15:59 ` Linus Torvalds
2010-11-10 16:46 ` Alexey Dobriyan
2010-11-10 16:55 ` Linus Torvalds
2010-11-10 17:10 ` Alexey Dobriyan
2010-11-10 18:55 ` Mark Lord
2010-11-10 18:27 ` Mike Galbraith
2010-11-10 23:43 ` Dave Chinner
2010-11-06 19:10 ` Arjan van de Ven
2010-11-07 17:16 ` Jesper Juhl
2010-11-09 19:47 ` Evgeniy Ivanov
2010-11-09 20:20 ` Christoph Hellwig
2010-11-09 21:00 ` Chris Mason
2010-10-31 1:22 ` Wu Fengguang
2010-10-31 1:51 ` Wu Fengguang
2010-11-01 1:09 ` Dimitrios Apostolou
2010-11-02 1:20 ` Wu Fengguang
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=1289401148-sup-3632@think \
--to=chris.mason@oracle.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=axboe@kernel.dk \
--cc=czoccolo@gmail.com \
--cc=damentz@gmail.com \
--cc=david@fromorbit.com \
--cc=db.pub.mail@gmail.com \
--cc=hch@infradead.org \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=penberg@kernel.org \
--cc=sanjoy@olin.edu \
--cc=shaohua.li@intel.com \
--cc=tglx@linutronix.de \
--cc=the.aidar@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).