From: Leroy van Logchem <leroy.vanlogchem@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] imporve jbd2 fsync batching
Date: Tue, 4 Nov 2008 22:15:35 +0000 (UTC) [thread overview]
Message-ID: <loom.20081104T221319-284@post.gmane.org> (raw)
In-Reply-To: 20081104205223.GW30291@mit.edu
> > + * can do, instead of having a static sleep time. This is usefull for
>
> s/usefull/useful/
and:
+ * join the transaction. We acheive this by measuring how long it takes
s/acheive/achieve/
--
Leroy
next prev parent reply other threads:[~2008-11-04 22:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 16:10 [PATCH] imporve jbd2 fsync batching Josef Bacik
2008-11-04 20:52 ` Theodore Tso
2008-11-04 22:15 ` Leroy van Logchem [this message]
2008-11-05 23:10 ` Andreas Dilger
2008-11-06 0:27 ` Theodore Tso
2008-11-06 12:45 ` Ric Wheeler
2008-11-25 10:22 ` [PATCH] ext4: add fsync batch tuning knobs Theodore Tso
2008-12-02 14:45 ` Aneesh Kumar K.V
2008-11-06 14:35 ` [PATCH] imporve jbd2 fsync batching Josef Bacik
2008-11-25 10:23 ` Theodore Tso
2008-11-25 22:41 ` Andreas Dilger
2008-11-26 5:10 ` Theodore Tso
2008-11-26 13:18 ` Josef Bacik
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=loom.20081104T221319-284@post.gmane.org \
--to=leroy.vanlogchem@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/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).