On Thu, 17 May 2001, Daniel Phillips wrote:
Well, if you look how I did the index, it works with blocks and buffers
while still staying entirely in the page cache. This was Stephen's
suggestion, and it integrates reliably with Al's page-oriented code.
So I'm mixing pages and blocks
On Friday 18 May 2001 11:10, Alexander Viro wrote:
On Thu, 17 May 2001, Daniel Phillips wrote:
Well, if you look how I did the index, it works with blocks and
buffers while still staying entirely in the page cache. This was
Stephen's suggestion, and it integrates reliably with Al's
Summary: ext3 works, page_launder() doesn't :)
The tree is based on the porting work which Peter Braam did. It's
in cvs in Jeff Garzik's home on sourceforge. Info on CVS is at
http://sourceforge.net/cvs/?group_id=3242 - the module name
is `ext3'. There's a README there which describes how
Andrew Morton wrote:
The tree is based on the porting work which Peter Braam did. It's
in cvs in Jeff Garzik's home on sourceforge. Info on CVS is at
http://sourceforge.net/cvs/?group_id=3242 - the module name
is `ext3'.
That was a bit cryptic.
cvs -d:pserver:[EMAIL
them once ext3/2.4
is steady. And once the pcache stuff is steady: the journalling
code is pretty complex.
It's probably worth thinking about adding a fourth journalling
mode: `journal=none'. Roll it all up into a single codebase
and call it ext4.
It rather depends on where the buffercache ends
Andrew writes:
It's probably worth thinking about adding a fourth journalling
mode: `journal=none'.
Yes, I had added this (at least in skeleton form) in my ext3 tree.
If only I could keep up with you and Daniel for both the ext3 and
indexed directory stuff, I might be able to submit it...
On Thursday 17 May 2001 17:53, Andrew Morton wrote:
It's probably worth thinking about adding a fourth journalling
mode: `journal=none'. Roll it all up into a single codebase
and call it ext4.
Or ext5 (= ext2 + ext3).
It rather depends on where the buffercache ends up. ext3 is
a client
AFAIK the original stated intention of ext3 was
cd linux/fs
cp -a ext2 ext3
# hack on ext3
That leaves ext2 in ultra-stability,
no-patches-unless-absolutely-necessary mode.
IMHO prove a new feature, like directories in page cache, journaling,
etc. in ext3 first. Then
On Thu, May 17, 2001 at 03:00:28PM -0400, Jeff Garzik wrote:
AFAIK the original stated intention of ext3 was
cd linux/fs
cp -a ext2 ext3
# hack on ext3
That leaves ext2 in ultra-stability,
no-patches-unless-absolutely-necessary mode.
IMHO prove a new feature, like
hi,
On May 17, 9:20pm, Andrew Morton wrote:
Subject: ext3 for 2.4
...
- quotas appear to work OK. I'll leave them turned on
as I test things, and watch out for oddities.
It's hard to find working quota tools. Most of them
either don't want to compile and/or don't understand
10 matches
Mail list logo
