From: Josef Bacik <jbacik@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: Josef Bacik <jbacik@redhat.com>,
tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] imporve jbd2 fsync batching
Date: Thu, 6 Nov 2008 09:35:01 -0500 [thread overview]
Message-ID: <20081106143459.GC18270@unused.rdu.redhat.com> (raw)
In-Reply-To: <20081105231012.GJ3184@webber.adilger.int>
On Wed, Nov 05, 2008 at 04:10:12PM -0700, Andreas Dilger wrote:
> On Nov 04, 2008 11:10 -0500, Josef Bacik wrote:
> > somebody does a sync write or an fsync() traditionally we would sleep for 1
> > jiffies, which depending on the value of HZ could be a significant amount of
> > time compared to how long it takes to commit a transaction to the underlying
> > storage. With this patch instead of sleeping for a jiffie, we check to see if
> > the amount of time this transaction has been running is less than the average
> > commit time, and if it is we sleep for the delta using schedule_hrtimeout to
> > give us a higher precision sleep time. This greatly benefits high end storage
> > where you could end up sleeping for longer than it takes to commit the
> > transaction and therefore sitting idle instead of allowing the transaction to
> > be committed by keeping the sleep time to a minimum so you are sure to always
> > be doing something.
>
> There was no reply to my previous comments about making the maximum sleep
> time be a fixed value (e.g. 15ms) instead of having it arbitrarily based
> on the jiffies value, which may change between 1ms and 10ms.
>
> I don't object to this being included in ext4, but I suspect it could do
> even better, or at least be more consistent than depending on the HZ value.
>
Sorry I missed that comment. The reason I set the top to be 1 jiffies was
because thats what it used to be, so in an effort to try and keep regressions
from happening I just left it as the max. I'm fine with setting the max to some
other more constant value. Thanks,
Josef
next prev parent reply other threads:[~2008-11-06 14:35 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
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 ` Josef Bacik [this message]
2008-11-25 10:23 ` [PATCH] imporve jbd2 fsync batching 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=20081106143459.GC18270@unused.rdu.redhat.com \
--to=jbacik@redhat.com \
--cc=adilger@sun.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).