From: Chris Mason <mason@suse.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Hans Reiser <reiser@namesys.com>, Oleg Drokin <green@namesys.com>,
Xuan Baldauf <xuan--reiserfs@baldauf.org>,
Reiserfs mail-list <Reiserfs-List@Namesys.COM>,
zam@thebsh.namesys.com
Subject: Re: Feature request: online fsync disable
Date: 23 Aug 2002 09:08:39 -0400 [thread overview]
Message-ID: <1030108119.17778.8.camel@tiny> (raw)
In-Reply-To: <15718.9718.736822.978374@laputa.namesys.com>
On Fri, 2002-08-23 at 08:09, Nikita Danilov wrote:
> Hans Reiser writes:
> > It is a reasonable feature request I think.
> >
> > Zam, put it into reiser4.1.
> >
>
> I think, in stead of feature "disable fsync", better alternative would
> be "disable journalling", or "journal meta-data only".
Well, if the application doesn't really need fsync, it shouldn't call
it. I'd much rather fix whatever problem is making things too slow.
Xuan, you could try the data logging patches in either data=writeback or
data=journal. Either one will be significantly faster than stock
2.4.19.
-chris
next prev parent reply other threads:[~2002-08-23 13:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 11:29 Feature request: online fsync disable Xuan Baldauf
2002-08-23 11:52 ` Nikita Danilov
2002-08-23 11:56 ` Oleg Drokin
2002-08-23 11:59 ` Hans Reiser
2002-08-23 12:09 ` Nikita Danilov
2002-08-23 13:08 ` Chris Mason [this message]
2002-08-23 18:10 ` Xuan Baldauf
2002-08-24 19:15 ` Chris Mason
2002-09-04 11:39 ` Xuan Baldauf
2002-09-04 12:13 ` Oleg Drokin
2002-08-25 21:21 ` Matthias Andree
2002-08-26 6:02 ` Valdis.Kletnieks
2002-08-25 21:20 ` Matthias Andree
2002-08-26 11:27 ` Hans Reiser
[not found] ` <20020905035604.GB6004@tapu.f00f.org>
2002-09-05 10:39 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2002-08-23 16:24 Xuan Baldauf
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=1030108119.17778.8.camel@tiny \
--to=mason@suse.com \
--cc=Nikita@Namesys.COM \
--cc=Reiserfs-List@Namesys.COM \
--cc=green@namesys.com \
--cc=reiser@namesys.com \
--cc=xuan--reiserfs@baldauf.org \
--cc=zam@thebsh.namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.