From: Theodore Ts'o <tytso@mit.edu>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Eric Sandeen <sandeen@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>,
mszeredi@suse.cz
Subject: Re: jbd2: don't wake kjournald unnecessarily
Date: Mon, 21 Jan 2013 18:11:30 -0500 [thread overview]
Message-ID: <20130121231130.GB12410@thunk.org> (raw)
In-Reply-To: <CA+icZUXLcdnNPvA9o8d5msOQ0MkMci8mPXujLZ3zcYjYcVZ7JQ@mail.gmail.com>
On Tue, Jan 22, 2013 at 12:04:32AM +0100, Sedat Dilek wrote:
>
> Beyond the FUSE/LOOP fun, will you apply this patch to your linux-next GIT tree?
>
> Feel free to add...
>
> Tested-by: Sedat Dilek <sedat.dilek@gmail.com>
>
> A similiar patch for JBD went through your tree into mainline (see [1] and [2]).
I'm not at all convinced that this patch has anything to do with your
problem. I don't see how it could affect things, and I believe you
mentioned that you saw the problem even with this patch applied? (I'm
not sure; some of your messages which you sent were hard to
understand, and you mentioned something about trying to send messages
when low on sleep :-).
In any case, the reason why I haven't pulled this patch into the ext4
tree is because I was waiting for Eric and some of the performance
team folks at Red Hat to supply some additional information about why
this commit was making a difference in performance for a particular
proprietary, closed source benchmark.
I'm very suspicious about applying patches under the "cargo cult"
school of programming. ("We don't understand why it makes a
difference, but it seems to be good, so bombs away!" :-)
Regards,
- Ted
next prev parent reply other threads:[~2013-01-21 23:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 23:44 jbd2: don't wake kjournald unnecessarily Sedat Dilek
2013-01-20 0:06 ` Sedat Dilek
2013-01-20 0:35 ` Sedat Dilek
2013-01-20 0:55 ` Sedat Dilek
2013-01-21 10:47 ` Jan Kara
2013-01-21 11:40 ` Sedat Dilek
2013-01-21 12:30 ` Sedat Dilek
2013-01-21 14:07 ` Jan Kara
2013-01-21 14:28 ` Sedat Dilek
2013-01-21 17:39 ` Miklos Szeredi
2013-01-21 23:04 ` Sedat Dilek
2013-01-21 23:11 ` Theodore Ts'o [this message]
2013-01-21 23:29 ` Sedat Dilek
2013-01-22 23:50 ` Jan Kara
2013-01-23 1:37 ` Eric Sandeen
2013-01-23 9:44 ` Jan Kara
2013-01-23 15:20 ` Eric Sandeen
2013-01-23 19:29 ` Jan Kara
2013-01-21 12:02 ` Carlos Maiolino
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=20130121231130.GB12410@thunk.org \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=sandeen@redhat.com \
--cc=sedat.dilek@gmail.com \
/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).