All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Daniel Phillips <phillips@phunq.net>,
	linux-fsdevel@vger.kernel.org, tux3@tux3.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [Tux3] Tux3 report: Tux3 Git tree available
Date: Thu, 12 Mar 2009 13:06:53 -0400	[thread overview]
Message-ID: <20090312170653.GC17104@mit.edu> (raw)
In-Reply-To: <200903122203.31502.nickpiggin@yahoo.com.au>

On Thu, Mar 12, 2009 at 10:03:31PM +1100, Nick Piggin wrote:
> It is basically already proven. It is faster with ext2 and it works with
> XFS delalloc, unwritten etc blocks (mostly -- except where I wasn't
> really able to grok XFS enough to convert it). And works with minix
> with larger block size than page size (except some places where core
> pagecache code needs some hacking that I haven't got around to).
> 
> Yes an ext3 conversion would probably reveal some tweaks or fixes to
> fsblock. I might try doing ext3 next. I suspect most of the problems
> would be fitting ext3 to much stricter checks and consistency required
> by fsblock, rather than adding ext3-required features to fsblock.
> 
> ext3 will be a tough one to convert because it is complex, very stable,
> and widely used so there are lots of reasons not to make big changes to
> it.

One possibility would be to do this with ext4 instead, since there are
fewer users, and it has more a "development" feel to it.  OTOH, there
are poeple (including myself) who are using ext4 in production
already, and I'd appreciate not having my source trees on my laptop
getting toasted.  :-)

Is it going to be possible to make the fsblock conversion being
something which is handled via CONFIG_EXT4_FSBLOCK #ifdefs, or are the
changes too invasive to really allow that?  (Also note BTW that ocfs2
is also using jbd2, so we need to be careful we don't break ocfs2
while we're doing the fsblock conversion.)

						- Ted

  parent reply	other threads:[~2009-03-12 17:07 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11 16:25 Tux3 report: Tux3 Git tree available Daniel Phillips
2009-03-11 18:42 ` Andrew Morton
2009-03-12  5:38   ` [Tux3] " Daniel Phillips
2009-03-12  6:07     ` Andrew Morton
2009-03-12  8:33       ` Daniel Phillips
2009-03-12  8:47         ` Nick Piggin
2009-03-12  9:00           ` Daniel Phillips
2009-03-12  9:10             ` Nick Piggin
2009-03-12 10:15               ` Daniel Phillips
2009-03-12 11:03                 ` Nick Piggin
2009-03-12 12:24                   ` Daniel Phillips
2009-03-12 12:32                     ` Matthew Wilcox
2009-03-12 12:45                       ` Nick Piggin
2009-03-12 12:45                         ` Nick Piggin
2009-03-12 13:12                         ` [Tux3] " Daniel Phillips
2009-03-12 13:06                       ` Daniel Phillips
2009-03-12 13:04                     ` Nick Piggin
2009-03-12 13:04                       ` Nick Piggin
2009-03-12 13:59                       ` [Tux3] " Matthew Wilcox
2009-03-12 14:19                         ` Nick Piggin
2009-03-15  3:24                         ` Daniel Phillips
2009-03-15  3:24                           ` Daniel Phillips
2009-03-15  3:50                           ` [Tux3] " Nick Piggin
2009-03-15  4:08                             ` Daniel Phillips
2009-03-15  4:08                               ` Daniel Phillips
2009-03-15  4:14                               ` [Tux3] " Nick Piggin
2009-03-15  2:41                       ` Daniel Phillips
2009-03-15  3:45                         ` Nick Piggin
2009-03-15 21:44                           ` Theodore Tso
2009-03-15 22:41                             ` Daniel Phillips
2009-03-16 10:32                               ` Nick Piggin
2009-03-16  5:12                             ` Dave Chinner
2009-03-16  5:12                               ` Dave Chinner
2009-03-16  6:38                               ` Theodore Tso
2009-03-16  6:38                                 ` Theodore Tso
2009-03-16 10:14                                 ` Nick Piggin
2009-03-16 10:14                                   ` Nick Piggin
2009-03-12 17:06                   ` Theodore Tso [this message]
2009-03-13  9:32                     ` [Tux3] " Nick Piggin
2009-03-12 17:00           ` OGAWA Hirofumi
2009-03-15  3:54             ` Daniel Phillips
2009-03-12  9:47         ` Sam Ravnborg
2009-03-12 10:25           ` Daniel Phillips
2009-03-12 15:30         ` Diego Calleja
2009-03-12 16:54         ` OGAWA Hirofumi
2009-03-15  3:36           ` Daniel Phillips
2009-03-15  4:26             ` OGAWA Hirofumi
2009-03-12 13:24       ` Andi Kleen
2009-03-12 21:24         ` [Tux3] " Daniel Phillips
2009-03-12 23:38           ` Andi Kleen
2009-03-15  3:03             ` Daniel Phillips
2009-03-12 21:02     ` Roland Dreier
2009-03-15  4:02       ` Daniel Phillips
2009-03-12 16:18   ` OGAWA Hirofumi
2009-03-12 20:02     ` Andrew Morton
2009-03-12 20:46       ` OGAWA Hirofumi
2009-03-15  3:58         ` Daniel Phillips

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=20090312170653.GC17104@mit.edu \
    --to=tytso@mit.edu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=phillips@phunq.net \
    --cc=tux3@tux3.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 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.