From: Jeff Garzik <jgarzik@pobox.com>
To: linux-fsdevel@vger.kernel.org
Subject: [bk patch] ibu filesystem
Date: Mon, 25 Aug 2003 19:56:28 -0400 [thread overview]
Message-ID: <20030825235628.GA13853@gtf.org> (raw)
At the moment, it's a mostly-boring filesystem. Local blkdev
filesystem, sortof an extent-based ext2. Gonna be playing around
with atomic metadata updates, runtime file optimizations, and other
goodies as time permits.
Features it does have: may even work. if you're really lucky, it won't
corrupt your data. bones for a background block reclaim (speeds up
unlink, maybe?). attempts to intelligently allocate blocks for some
cases, with file size hueristics mostly. probably some other stuff I
don't remember :)
The only recent change is rediffing ibu against 2.4.22.
A bare-bones mkfs util is in CVS at
http://sourceforge.net/projects/fstools/
which may or may not work.
Insane BK users may issue a
bk pull bk://kernel.bkbits.net/jgarzik/ibu-2.4
Others nutters may download the patch from
ftp://ftp.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.4/2.4.22-ibu1.patch.bz2
This will update the following files:
fs/Config.in | 2
fs/Makefile | 1
fs/ibu/Makefile | 11 +
fs/ibu/aops.c | 317 ++++++++++++++++++++++++++++
fs/ibu/balloc.c | 377 ++++++++++++++++++++++++++++++++++
fs/ibu/dir.c | 603 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
fs/ibu/file.c | 58 +++++
fs/ibu/fsync.c | 56 +++++
fs/ibu/ibu-raw.h | 185 ++++++++++++++++
fs/ibu/ibu.h | 274 +++++++++++++++++++++++-
fs/ibu/imap.c | 325 +++++++++++++++++++++++++++++
fs/ibu/inode.c | 416 +++++++++++++++++++++++++++++++++++++
fs/ibu/ioctl.c | 94 ++++++++
fs/ibu/msg.c | 85 +++++++
fs/ibu/namei.c | 345 +++++++++++++++++++++++++++++++
fs/ibu/super.c | 517 +++++++++++++++++++++++++++++++++++++++++++++++
fs/ibu/symlink.c | 44 ++++
17 files changed, 3690 insertions(+), 20 deletions(-)
reply other threads:[~2003-08-25 23:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030825235628.GA13853@gtf.org \
--to=jgarzik@pobox.com \
--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