public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Lord <lord@sgi.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@zip.com.au>,
	Mike Fedyk <mfedyk@matchmail.com>,
	Guillaume Boissiere <boissiere@attbi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [STATUS 2.5]  May 1, 2002
Date: 01 May 2002 22:29:17 -0500	[thread overview]
Message-ID: <1020310158.8097.45.camel@localhost.localdomain> (raw)
In-Reply-To: <m1adrjz1f0.fsf@frodo.biederman.org>

On Wed, 2002-05-01 at 22:14, Eric W. Biederman wrote:
> Stephen Lord <lord@sgi.com> writes:
> > 
> > Most of the performance benefits of delayed allocate are that
> > you do not the hard work of allocating the disk space in each
> > write call, you get to do it once, in potentially larger chunks,
> > and often not in the user's context.
> 
> Except for moving the work out of the users context, ext2 gets
> a similar benefit by reserving disk space ahead of time.  So it isn't
> clear that you need to have a delayed allocation to achieve this.
> 
> Eric

Doesn't everyone reserve more than the write asks for?

Delayed allocation as implemented in XFS means that during a write
call which has to make more room in a file, a super block counter
is changed, and the extent information is recorded in an in memory
structure associated with the inode.

Yes, if you have all your metadata buffers sitting in memory and are
not journalling changes then all you are doing is a different set of
memory manipulations which are noise on modern cpus when compared with
actually moving the file data out to disk.

Steve



      reply	other threads:[~2002-05-02  3:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-01 13:53 [STATUS 2.5] May 1, 2002 Guillaume Boissiere
2002-05-01 15:06 ` [STATUS 2.5] May 1, 2002 (BKL status) Dave Hansen
2002-05-02 11:10   ` Guillaume Boissiere
2002-05-01 20:19 ` [STATUS 2.5] May 1, 2002 Mike Fedyk
2002-05-01 21:38   ` Andrew Morton
2002-05-02  1:11     ` Stephen Lord
2002-05-02  3:14       ` Eric W. Biederman
2002-05-02  3:29         ` Stephen Lord [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=1020310158.8097.45.camel@localhost.localdomain \
    --to=lord@sgi.com \
    --cc=akpm@zip.com.au \
    --cc=boissiere@attbi.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.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