From: Andrew Morton <akpm@zip.com.au>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre10aa1
Date: Thu, 06 Jun 2002 18:58:59 -0700 [thread overview]
Message-ID: <3D001363.BDEBD682@zip.com.au> (raw)
In-Reply-To: <20020607003413.GH1004@dualathlon.random>
Andrea Arcangeli wrote:
>
> ...
> Only in 2.4.19pre10aa1: 90_ext3-commit-interval-1
>
> Avoid laptops to waste energy despite kupdate interval is set
> to 2 hours with ext3. kjournald has no right to choose
> "how frequently" we should look for old transactions, that's
> an user problem. journaling doesn't enforce how much old data
> we can lose after a 'reboot -f', it only enforces that the
> metadata or even the data will be coherent after an hard reboot.
Yes, that'll work OK. It's a wild implementation though. Why not
just add
int bdflush_min(void)
{
return bdf_prm.b_un.interval;
}
EXPORT_SYMBOL(bdflush_min);
to fs/buffer.c?
(You forgot to export bdf_prm, btw).
-
next prev parent reply other threads:[~2002-06-07 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 0:34 2.4.19pre10aa1 Andrea Arcangeli
2002-06-07 1:58 ` Andrew Morton [this message]
2002-06-07 2:08 ` 2.4.19pre10aa1 Andrea Arcangeli
2002-06-07 15:10 ` 2.4.19pre10aa1 J.A. Magallon
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=3D001363.BDEBD682@zip.com.au \
--to=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=linux-kernel@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