From: Joel Becker <Joel.Becker@oracle.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: Proposal and plan for ext2/3 future development work
Date: Thu, 29 Jun 2006 18:59:03 -0700 [thread overview]
Message-ID: <20060630015903.GE11640@ca-server1.us.oracle.com> (raw)
In-Reply-To: <44A47B0D.7020308@garzik.org>
On Thu, Jun 29, 2006 at 09:14:53PM -0400, Jeff Garzik wrote:
> Agreed overall, though specifically for delayed allocation I think
> that's an ext4 thing:
>
> * First off, I'm a big fan of delalloc, and (like extents) definitely
> want to see the feature implemented
> * Delayed allocation, properly done, requires careful interaction with
> VM writeback (memory pressure or normal writeout), and may require some
> minor changes to generic code in fs/* and mm/*
To be honest, I'd like to see more delayed allocation
infrastructure in the VFS itself. XFS has to maintain an entire chunk
of state for it, and I suspect ext4 will as well. I'd love to get
delayed allocation into OCFS2 someday. Why not move to where we can
share the in-memory accounting code?
Now, we'd probably want to start by prototyping it in ext4
directly. Once it's stable as a filesystem feature, we can see where
XFS and ext4 overlap, etc, etc. But I'd like to keep a more generic
direction in mind.
Joel
--
"The suffering man ought really to consume his own smoke; there is no
good in emitting smoke till you have made it into fire."
- thomas carlyle
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2006-06-30 1:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 23:55 Proposal and plan for ext2/3 future development work Theodore Ts'o
2006-06-30 1:14 ` Jeff Garzik
2006-06-30 1:59 ` Joel Becker [this message]
2006-06-30 17:13 ` Badari Pulavarty
2006-06-30 18:24 ` Joel Becker
2006-06-30 19:17 ` Steve Lord
2006-06-30 19:29 ` Badari Pulavarty
2006-06-30 10:39 ` Andi Kleen
2006-06-30 15:14 ` Theodore Tso
2006-07-01 9:42 ` Adrian Bunk
2006-07-01 10:29 ` Theodore Tso
2006-06-30 11:09 ` Patrick McFarland
2006-06-30 23:44 ` Mingming Cao
2006-07-24 13:04 ` Guillaume Chazarain
2006-07-24 18:11 ` Jeff Garzik
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=20060630015903.GE11640@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).