From: "Ramy M. Hassan" <ramy@gawab.com>
To: <linux-kernel@vger.kernel.org>
Subject: Advanced storage management ( suggestion )
Date: Fri, 5 Mar 2004 21:44:20 +0200 [thread overview]
Message-ID: <003801c402ea$44437190$ba10a8c0@ramy> (raw)
I see many people interested in designing of new filesystems for
different purposes, and one of the common tasks all filesystem designers
will do is to manage device blocks.
I just thought of starting a new project that aims to create an
advanced, scalable and high performance block level storage management
layer for the Linux kernel.
This layer should provide low level storage services to simplify the
development of filesystems, DBMS, LDAP servers, or any other
applications that require high performance storage.
The planned features are :
1- Very fast block allocation ( Using balanced trees for tracking free
blocks comes into my mind now, but I still it is early to decide the
design ).
2- Support for multi-disk/multi-host storage pool.
3- Meta data storage and block storage can be isolated for better
performance.
4- Meta data and block replication options.
5- Transactional options for journaling filesystems or transactional
databases.
6- Supports clustering through lock managers where multiple hosts can
read/write to same storage devices concurrently ( suitable for SANs )
7- Transparent recovery from corruption or hardware failure.
8- Direct access from userland ( for DBMS, LDAP, and other userland
applications ).
9- Plugins support ( like those of reiserfs 4).
If you know of any similar effort, or any technical obstacle I am
missing , please let me know.
Ramy
next reply other threads:[~2004-03-05 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 19:44 Ramy M. Hassan [this message]
2004-03-07 3:34 ` Mike Fedyk
2004-03-07 4:30 ` Neil Brown
2004-03-07 6:08 ` Mike Fedyk
2004-03-09 16:38 ` Jeremy Jackson
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='003801c402ea$44437190$ba10a8c0@ramy' \
--to=ramy@gawab.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®