From: Andrew Morton <akpm@osdl.org>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: hch@infradead.org, aia21@cam.ac.uk, torvalds@osdl.org,
linux-kernel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net
Subject: Re: NTFS
Date: Thu, 18 Jan 2007 16:17:41 -0800 [thread overview]
Message-ID: <20070118161741.6ac4e423.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0701190022540.17626@alpha.polcom.net>
> On Fri, 19 Jan 2007 00:27:17 +0100 (CET) Grzegorz Kulewski <kangur@polcom.net> wrote:
> On Thu, 18 Jan 2007, Andrew Morton wrote:
> >> On Thu, 18 Jan 2007 22:38:13 +0000 Christoph Hellwig <hch@infradead.org> wrote:
> >> On Thu, Jan 18, 2007 at 02:35:06PM -0800, Andrew Morton wrote:
> >>>> Cool. That means ->put_inode is gone in -mm. Andrew, what are the
> >>>> plans for sending the patches to make the ext2 preallocation work
> >>>> like ext3 to Linus?
> >>>
> >>> Cautious. I'm not sure that we ever want to merge them, really - ext2 is
> >>> more a reference filesystem than a real one nowadays, and making it more
> >>> complex detracts from that.
> >>
> >> The again while the old preallocation code might be simpler it's also utterly
> >> braindead and we need to make sure no one is going to copy this :)
> >
> > Good point ;)
>
> Are you refering to that particular implementation in ext2 or to the
> whole method od doing it implemented currently in ext2?
It's a patch which cross-ports ext3's block-reservation code into ext2.
> When can I read about it (description of the new method/implementation in
> ext3 and why is it better) some more?
Hard. google(ext3 reservations) is a starting point.
prev parent reply other threads:[~2007-01-19 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 10:25 NTFS Anton Altaparmakov
2007-01-18 22:22 ` NTFS Christoph Hellwig
[not found] ` <20070118143506.4d007aad.akpm@osdl.org>
2007-01-18 22:38 ` NTFS Christoph Hellwig
2007-01-18 22:54 ` NTFS Andrew Morton
2007-01-18 23:27 ` NTFS Grzegorz Kulewski
2007-01-19 0:17 ` Andrew Morton [this message]
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=20070118161741.6ac4e423.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=aia21@cam.ac.uk \
--cc=hch@infradead.org \
--cc=kangur@polcom.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®