From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: jbd2 batch time tuning behavior question
Date: Mon, 02 Jun 2014 10:00:05 -0500 [thread overview]
Message-ID: <538C9175.7010003@redhat.com> (raw)
In-Reply-To: <20140602144210.GC30598@thunk.org>
On 6/2/14, 9:42 AM, Theodore Ts'o wrote:
> On Tue, May 27, 2014 at 11:47:06AM -0500, Eric Sandeen wrote:
>>
>> Docs say "0" turns it off, but option handling turns "0" into
>> EXT4_DEF_MAX_BATCH_TIME. What was the real intent here; should the
>> docs or the behavior be changed?
>
> Nice catch! I would think it's probably better if we make the
> behavior change to match the docs.
>
> Want to send a patch, since you found the problem, or shall I create a
> patch myself to fix things up?
>
> Thanks,
>
> - Ted
>
I can send the patch, I just wondered what the intent was.
Thanks,
-Eric
prev parent reply other threads:[~2014-06-02 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 16:47 jbd2 batch time tuning behavior question Eric Sandeen
2014-06-02 14:42 ` Theodore Ts'o
2014-06-02 15:00 ` Eric Sandeen [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=538C9175.7010003@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@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 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).