All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: "Grzegorz Jaśkiewicz" <gryzman@gmail.com>
Cc: reiserfs-list@namesys.com, reiserfs-dev@namesys.com
Subject: Re: Why reiser does a disk write on every sync() call?
Date: Wed, 16 May 2007 19:32:33 +0400	[thread overview]
Message-ID: <200705161932.34390.vs@namesys.com> (raw)
In-Reply-To: <2f4958ff0705120603x4da5bcdq2c48c9394586f6c@mail.gmail.com>

Hello

On Saturday 12 May 2007 17:03, Grzegorz Jaśkiewicz wrote:
> sounds like useless waste of time and space
> You haven't stated the reason, why it has to create and commit empty
> transaction.
> 

I think we should fix that.

Chris, do you think that we could avoid creating fake transactions with the below patch?


diff -puN fs/reiserfs/super.c~reiserfs-avoid-syncing-clean-fs fs/reiserfs/super.c
--- linux-2.6.21-mm2/fs/reiserfs/super.c~reiserfs-avoid-syncing-clean-fs	2007-05-16 18:18:45.000000000 +0300
+++ linux-2.6.21-mm2-vs/fs/reiserfs/super.c	2007-05-16 18:19:06.000000000 +0300
@@ -62,7 +62,7 @@ static int reiserfs_statfs(struct dentry
 
 static int reiserfs_sync_fs(struct super_block *s, int wait)
 {
-	if (!(s->s_flags & MS_RDONLY)) {
+	if (!(s->s_flags & MS_RDONLY) && s->s_dirt) {
 		struct reiserfs_transaction_handle th;
 		reiserfs_write_lock(s);
 		if (!journal_begin(&th, s, 1))

_

      parent reply	other threads:[~2007-05-16 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1174932216.16988.ezmlm@namesys.com>
2007-03-26 18:12 ` Why reiser does a disk write on every sync() call? Lin Shen (lshen)
2007-03-27  7:59   ` Vladimir V. Saveliev
2007-03-27 17:20     ` Lin Shen (lshen)
2007-03-27 18:54       ` Vladimir V. Saveliev
2007-05-12 13:03         ` Grzegorz Jaśkiewicz
2007-05-12 14:56           ` Toby Thain
2007-05-16 15:32           ` Vladimir V. Saveliev [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=200705161932.34390.vs@namesys.com \
    --to=vs@namesys.com \
    --cc=gryzman@gmail.com \
    --cc=reiserfs-dev@namesys.com \
    --cc=reiserfs-list@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.