linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: "Ted Ts'o" <tytso@mit.edu>,
	sedat.dilek@gmail.com, Curt Wohlgemuth <curtw@google.com>,
	linux-ext4@vger.kernel.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vg
Cc: "s.dilek" <s.dilek@jpberlin.de>
Subject: Re: [ext4] Multiple page-io submission (Option "mblk_io_submit")
Date: Wed, 23 Mar 2011 08:32:28 +0100	[thread overview]
Message-ID: <AANLkTi=4k7QrtPg1B7bbzNzVMjj_aKwq99+DByQo2BP6@mail.gmail.com> (raw)
In-Reply-To: <20110209183816.GD9533@thunk.org>

On Wed, Feb 9, 2011 at 7:38 PM, Ted Ts'o <tytso@mit.edu> wrote:
> On Tue, Feb 08, 2011 at 06:30:29PM +0100, Sedat Dilek wrote:
>> Hi,
>>
>> while looking at pending patches in ext4.git#{master, for_linus}, I
>> saw "ext4: Fix data corruption with multi-block writepages support"
>> which should fix [2] according to text in the commit-body.
>>
>> Are you planning to turn on "multiple page-io submission" again by
>> default (as is was disabled in "ext4: Turn off multiple page-io
>> submission by default" [3])?
>
> I'm planning on turning it on by default post 2.6.38, during the
> 2.6.39-rc1 merge window.  That's me being paranoid, since this is so
> late in the -rc cycle for 2.6.38.
>
>                                                - Ted
>

Ping!
(As the merge-window is still open.)

- Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2011-03-23  7:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 17:30 [ext4] Multiple page-io submission (Option "mblk_io_submit") Sedat Dilek
2011-02-09 18:38 ` Ted Ts'o
2011-03-23  7:32   ` Sedat Dilek [this message]

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='AANLkTi=4k7QrtPg1B7bbzNzVMjj_aKwq99+DByQo2BP6@mail.gmail.com' \
    --to=sedat.dilek@googlemail.com \
    --cc=curtw@google.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vg \
    --cc=s.dilek@jpberlin.de \
    --cc=sedat.dilek@gmail.com \
    --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).