linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Tomas <alex@clusterfs.com>
To: David Chinner <dgc@sgi.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	ext4 development <linux-ext4@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC] basic delayed allocation in VFS
Date: Sun, 29 Jul 2007 16:09:20 +0400	[thread overview]
Message-ID: <46AC8370.8050308@clusterfs.com> (raw)
In-Reply-To: <20070729091807.GF31489@sgi.com>

David Chinner wrote:
> On Fri, Jul 27, 2007 at 11:51:56AM +0400, Alex Tomas wrote:
> But this is really irrelevant - the issue at hand is what we want
> for VFS level delalloc support. IMO, that mechanism needs to support
> both XFS and ext4, and I'd prefer if it doesn't perpetuate the
> bufferhead abuses of the past (i.e. define an iomap structure
> instead of overloading bufferheads yet again).

I'm not sure I understand very well. where would you track uptodate,
dirty and other states then? do you propose to separate block states
from block mapping?

thanks, Alex

  reply	other threads:[~2007-07-29 12:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26  8:59 [RFC] basic delayed allocation in VFS Alex Tomas
2007-07-26 10:32 ` Jeff Garzik
2007-07-26 10:35   ` Alex Tomas
2007-07-26 12:05     ` Jeff Garzik
2007-07-26 13:33       ` Alex Tomas
2007-07-27  5:07         ` David Chinner
2007-07-27  7:51           ` Alex Tomas
2007-07-27 12:33             ` Jeff Garzik
2007-07-27 12:42               ` Alex Tomas
2007-07-28 19:56             ` Christoph Hellwig
2007-07-29  9:18             ` David Chinner
2007-07-29 12:09               ` Alex Tomas [this message]
2007-07-30  0:29                 ` David Chinner
2007-07-27 12:38           ` Alex Tomas
2007-07-28 19:57             ` Christoph Hellwig
2007-07-28 19:53           ` Christoph Hellwig
2007-07-28 19:51   ` Christoph Hellwig
2007-07-28 19:56     ` Alex Tomas
2007-07-29 17:30     ` Andreas Dilger
2007-07-29 17:48       ` Alex Tomas
2007-07-29 19:22         ` Christoph Hellwig
2007-07-29 19:24       ` Christoph Hellwig
2007-07-29 19:51         ` Alex Tomas
2007-07-30  0:28         ` Theodore Tso
2007-07-30 17:49         ` Mingming Cao
2007-07-30 19:43           ` Andrew Morton
2007-07-26 11:47 ` Aneesh Kumar K.V

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=46AC8370.8050308@clusterfs.com \
    --to=alex@clusterfs.com \
    --cc=dgc@sgi.com \
    --cc=hch@infradead.org \
    --cc=jeff@garzik.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    /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).