All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Guillaume Boissiere <boissiere@attbi.com>, linux-kernel@vger.kernel.org
Subject: Re: [STATUS 2.5]  May 1, 2002
Date: Wed, 01 May 2002 14:38:37 -0700	[thread overview]
Message-ID: <3CD0605D.ACC42AA2@zip.com.au> (raw)
In-Reply-To: <3CCFBB21.9046.7889B0D2@localhost> <20020501201927.GS574@matchmail.com>

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.

There are other reasons for implementing delalloc
(XFS, improved layout, ...).  So it ain't dead yet.


At 48 bytes, 2.5's buffer_head is now precisely half the
size of 2.4's.  I'm hoping to be able to shed another eight
bytes yet.

With the pagecache<->BIO change, the buffer_head will most
definitely become "per-page metadata which describes the state
of sub-page segments" and not "something which is used for
performing I/O".



-

  reply	other threads:[~2002-05-01 21:39 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 [this message]
2002-05-02  1:11     ` Stephen Lord
2002-05-02  3:14       ` Eric W. Biederman
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=3CD0605D.ACC42AA2@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=boissiere@attbi.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 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.