linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Koss <kossjan@gmail.com>
To: kernelnewbies@nl.linux.org, linux-fsdevel@vger.kernel.org
Subject: dummy fs
Date: Wed, 11 Jan 2006 20:18:57 +0300	[thread overview]
Message-ID: <b97d23040601110918v6a9440d9n63f312d8b1b481e0@mail.gmail.com> (raw)

Hello.

I want implement educational file-system for Linux.
I suppose it would be very simplified UFS (for example,
with such limitations like: size of file <=8K, length of name <20 characters
and so on). The main goal is simplicity, small size of implementation
and space for speedup improvements.

1)May be some one hear about such for Linux 2.6 ?

2)Currently I'm investigating how "truncate" method should works on
the filesystem layer.
Is any description how it should works?
I mean, as I understand first I should truncate page cache
(block_truncate_page?),
what about "buffer_head" which now not belong to my file and may be
used by another process at the same time?

3)As I see sb_find_get_block return "buffer_head", with b_count==2,
(if nobody before use this "buffer_head"),
is it right behavior?
Should I call two time brelse to free "buffer_head",
which I get using sb_find_get_block?

4)Is there set of tests to check work of ordinary Unix file-system?
For example: one process creates files, and another check using
(readdir) is all right,
one open file for writing, another open the same file for reading... etc

             reply	other threads:[~2006-01-11 17:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 17:18 Jan Koss [this message]
2006-01-12 14:52 ` dummy fs Tyler
2006-01-12 17:31   ` Greg KH

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=b97d23040601110918v6a9440d9n63f312d8b1b481e0@mail.gmail.com \
    --to=kossjan@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --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;
as well as URLs for NNTP newsgroup(s).