linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Stephen Tweedie <sct@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Patch 6/7] 2.4.20-pre4/ext3: jbd commit interval tuning
Date: Fri, 27 Sep 2002 23:48:33 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209272346380.17618-100000@freak.distro.conectiva> (raw)
In-Reply-To: <200209261355.g8QDtWh17010@sisko.scot.redhat.com>



On Thu, 26 Sep 2002, Stephen Tweedie wrote:

> Allow an arbitrary commit interval to be set when mounting or remounting
> a filesystem.
>
> Note that if this is greater than the system bdflush interval, then the
> regular sync()s will beat the commit timer and you won't get longer
> commit timeouts.

Applied. For 2.5 we probably want all fs'es to have the same string to set
the commit interval.


      reply	other threads:[~2002-09-28  4:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-26 13:55 [Patch 6/7] 2.4.20-pre4/ext3: jbd commit interval tuning Stephen Tweedie
2002-09-28  2:48 ` Marcelo Tosatti [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=Pine.LNX.4.44.0209272346380.17618-100000@freak.distro.conectiva \
    --to=marcelo@conectiva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.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).