linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Xin Zhao <uszhaoxin@gmail.com>
Cc: mingz@ele.uri.edu, mikado4vn@gmail.com,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: Question regarding to store file system metadata in database
Date: Sun, 19 Mar 2006 19:47:23 +0000	[thread overview]
Message-ID: <20060319194723.GA27946@ftp.linux.org.uk> (raw)
In-Reply-To: <4ae3c140603191050k3bf7e960q9b35fe098e2fbe35@mail.gmail.com>

On Sun, Mar 19, 2006 at 01:50:22PM -0500, Xin Zhao wrote:
> Last, database-based file system is not so complex. As first step, I
> am just proposing to store pathanem-to-inode number in database. So it
> is basically a simple table. We don't really need any fancy features
> provided by db system. That's why I said a reduced  db system is
> enough. So the only difference betwen db-based file system and a
> regular one is that regular file system use directory file to store
> entries, but db-based file system use database to achieve the same
> goal. Looks like db will be a more efficient way. ;-)

Define "database".  And explain how any of existing filesystems manages
to _not_ qualify your definition.

As for "more efficient"...  300 lookups per second is less than an
improvement.  It's orders of magnitude worse than e.g. ext2; I don't
know in which world that would be considered more efficient, but I
certainly glad that I don't live there.

  reply	other threads:[~2006-03-19 19:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-19  4:48 Question regarding to store file system metadata in database Xin Zhao
2006-03-19  5:07 ` Mikado
2006-03-19 17:48   ` Xin Zhao
2006-03-19 17:58     ` Ming Zhang
2006-03-19 18:11       ` Xin Zhao
2006-03-19 18:26         ` Ming Zhang
2006-03-19 18:50           ` Xin Zhao
2006-03-19 19:47             ` Al Viro [this message]
     [not found]               ` <441DC2D6.4060001@societasilluminati.org>
2006-03-19 21:24                 ` Ming Zhang
2006-03-20 13:09               ` Theodore Ts'o
2006-03-20 15:13                 ` Xin Zhao
2006-03-20 19:36                   ` Xin Zhao
2006-03-20 19:58                     ` Al Viro
2006-03-20 22:53                       ` Xin Zhao
2006-03-20 23:32                         ` Al Viro
2006-03-20 21:08                     ` Matti Aarnio
2006-03-20 22:28                     ` Erez Zadok
2006-03-20 22:19                   ` Theodore Ts'o
2006-03-21  6:51                     ` Miklos Szeredi
2006-03-21 20:05                   ` Pavel Machek
2006-03-22 15:21                     ` Xin Zhao
2006-03-19 21:34             ` Ming Zhang
2006-03-20  8:30         ` Matti Aarnio
2006-03-19 23:06 ` Alan Cox
2006-03-19 23:44   ` Matthew Wilcox

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=20060319194723.GA27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikado4vn@gmail.com \
    --cc=mingz@ele.uri.edu \
    --cc=uszhaoxin@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).