mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Zarochentcev <zam@namesys.com>
To: reiser@namesys.com
Cc: Nikita Danilov <Nikita@namesys.com>,
	Tomas Szepe <szepe@pinerecords.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Oleg Drokin <green@namesys.com>, umka <umka@namesys.com>
Subject: Re: [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply
Date: Tue, 5 Nov 2002 11:49:16 +0300	[thread overview]
Message-ID: <15815.34316.24237.515178@crimson.namesys.com> (raw)
In-Reply-To: <3DC784E3.2090001@namesys.com>

reiser writes:
 > Alexander Zarochentcev wrote:
 > 
 > > > >
 > > > >In reiser4 allocation of disk space is delayed to transaction commit. It
 > > > >is not possible to estimate precisely amount of disk space that will be
 > > > >allocated during commit, and hence statfs(2) results are not updated
 > > > >until one does sync(2) (forcing commit) or transaction is committed due
 > > > >to age (10 minutes by default).
 > > > >
 > > > >  
 > > > >
 > > > The above is badly phrased, and the behavior complained of is indeed a 
 > > > bug not a feature.  Please fix.  
 > > > 
 > > > statfs should be updated immediately in accordance with estimates used 
 > > > by the space reservation code, and then adjusted at commit time in 
 > > > accordance with actual usage.
 > >
 > >We should not do that unless we implement forcing of commits at out of free
 > >space situation.
 > >
 > I thought we had agreed to do forcing of commits at out of free space 
 > quite some time ago?  In any event, we should do forcing of commits at 
 > out of free space.  Yes?

we will control this by a block allocator flag, we set it when we can close
current transaction. I think for most cases it will be set.
 

-- 
Alex.

  reply	other threads:[~2002-11-05  8:47 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 21:23 [BK][PATCH] Reiser4, will double Linux FS performance, please apply Hans Reiser
2002-10-31 22:34 ` Dieter Nützel
2002-10-31 22:47   ` Hans Reiser
2002-11-01  1:17     ` [BK][PATCH] Reiser4, will double Linux FS performance, pleaseapply Andrew Morton
2002-11-01  1:27       ` Andrew Morton
2002-11-01  1:27       ` Hans Reiser
2002-11-01  1:33         ` Andrew Morton
2002-11-01  1:44           ` Dieter Nützel
2002-11-01  1:55           ` Hans Reiser
2002-11-01 10:23             ` Tomas Szepe
2002-11-01 17:19               ` Alexander Zarochentcev
2002-11-02 13:24                 ` Tomas Szepe
2002-11-04 11:00                   ` Nikita Danilov
2002-11-04 19:56                     ` Andreas Dilger
2002-11-05  7:30                     ` reiser
2002-11-05  8:28                       ` Alexander Zarochentcev
2002-11-05  8:44                         ` reiser
2002-11-05  8:49                           ` Alexander Zarochentcev [this message]
2002-11-05 21:08                             ` reiser
2002-11-05  9:29                       ` Andreas Dilger
2002-11-05 21:39                         ` reiser
2002-11-05  9:59                       ` Tomas Szepe
2002-11-05 10:08                         ` Alexander Zarochentcev
2002-11-05 10:23                           ` Tomas Szepe
2002-11-05 10:46                         ` Nikita Danilov
2002-11-02 13:38                 ` Tomas Szepe
2002-11-04 12:02                   ` Nikita Danilov
2002-11-04 17:10                     ` Tomas Szepe
2002-11-04 17:53                       ` Nikita Danilov
2002-11-04 18:10                         ` Tomas Szepe
2002-11-01  4:36           ` Linus Torvalds
2002-11-01 10:59             ` Nikita Danilov
     [not found] <877555917@toto.iv>
2002-11-05 23:09 ` Peter Chubb
2002-11-06  1:33   ` reiser
2002-11-06 14:25     ` Daniel Egger
2002-11-07 17:19       ` Pavel Machek
2002-11-07 16:58     ` Bill Davidsen
2002-11-06 18:37 Tom Reinhart

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=15815.34316.24237.515178@crimson.namesys.com \
    --to=zam@namesys.com \
    --cc=Nikita@namesys.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=szepe@pinerecords.com \
    --cc=umka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®