public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
	Beau Kuiper <kuib-kl@ljbc.wa.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Significant performace improvements on reiserfs systems, kupdated bugfixes
Date: Sun, 23 Sep 2001 11:24:00 -0400	[thread overview]
Message-ID: <1903280000.1001258640@tiny> (raw)
In-Reply-To: <20010922213218.D31000@emma1.emma.line.org>
In-Reply-To: <20010921152627.C13862@emma1.emma.line.org> <Pine.LNX.4.30.0109230226210.25332-100000@gamma.student.ljbc> <20010922213218.D31000@emma1.emma.line.org>



On Saturday, September 22, 2001 09:32:18 PM +0200 Matthias Andree
<matthias.andree@stud.uni-dortmund.de> wrote:
> On Sun, 23 Sep 2001, Beau Kuiper wrote:
>
>> This code change does not affect the functionality of fsync(), only
>> kupdated. kupdated is responsible for flushing buffers that have been
>> sitting around too long to disk.

Correct, fsync is unchanged, but sync() does rely on the super dirty bit.
If the super isn't dirty, then sync doesn't try to force metadata to disk
at all.

> 
> Sorry, I didn't grok that when writing my previous mail in this thread.
> I thought kupdate was the one that writes ReiserFS transactions, but
> that's kreiserfsd, I think.

Well, kreiserfsd usually writes the log blocks, when a transaction ends on
its own (full, or too old).  If someone requests a synchronous commit
(fsync, any caller of write_super), that process writes the log blocks
themselves.  So, kupdated ends up writing log blocks too.

Plus, reiserfs uses write_super as a trigger for metadata writeback, so
kupdate writes those blocks as well.

-chris


  reply	other threads:[~2001-09-23 15:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20  7:12 [PATCH] Significant performace improvements on reiserfs systems, kupdated bugfixes Beau Kuiper
2001-09-20 12:16 ` Chris Mason
2001-09-20 15:20   ` Beau Kuiper
2001-09-20 16:15     ` Andreas Dilger
2001-09-20 16:22       ` Beau Kuiper
2001-09-21 20:12         ` Lehmann 
2001-09-21 20:57           ` Rik van Riel
2001-09-21 22:50             ` Lehmann 
2001-09-21 13:26 ` Matthias Andree
2001-09-22 18:38   ` Beau Kuiper
2001-09-22 19:32     ` Matthias Andree
2001-09-23 15:24       ` Chris Mason [this message]
2001-09-24 14:37   ` Stephen C. Tweedie
  -- strict thread matches above, loose matches on Subject: below --
2001-09-20 17:23 Chris Mason

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=1903280000.1001258640@tiny \
    --to=mason@suse.com \
    --cc=kuib-kl@ljbc.wa.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.de \
    /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