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
(You forgot to export bdf_prm, btw).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 07 2002 - 22:00:29 EST