public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Stephen Lord <lord@sgi.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 21:14:27 -0600	[thread overview]
Message-ID: <m1adrjz1f0.fsf@frodo.biederman.org> (raw)
In-Reply-To: <3CCFBB21.9046.7889B0D2@localhost> <20020501201927.GS574@matchmail.com> <3CD0605D.ACC42AA2@zip.com.au> <1020301894.1171.2.camel@localhost.localdomain>

Stephen Lord <lord@sgi.com> writes:

> On Wed, 2002-05-01 at 16:38, Andrew Morton wrote:
> > Mike Fedyk wrote:
> > > 
> > > On Wed, May 01, 2002 at 09:53:37AM -0400, Guillaume Boissiere wrote:
> > > > new framebuffer layer, as well as some more delayed disk block
> > > > allocation bits.
> > > 
> > > Actually Andrews work on address_space based writeback is related somewhat,
> > > but really it's a rewrite/cleanup of the buffer layer.  Delayed block
> > > alocation is helped alot by this, and almost depends on it IIRC.
> > > 
> > > One vote for a seperate listing in the status for "Address Space based
> > > Writeback / Buffer layer cleanup".
> > 
> > Well the next major step here is going direct
> > pagecache<->BIO, bypassing the intermediate submit_bh
> > for most I/O.
> > 
> > Probably that will make most of the performance benefits
> > of delayed-allocate go away.
> 
> 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

  reply	other threads:[~2002-05-02  3:22 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 [this message]
2002-05-02  3:29         ` Stephen Lord

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=m1adrjz1f0.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=akpm@zip.com.au \
    --cc=boissiere@attbi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lord@sgi.com \
    --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