linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@gmx.de>
To: Maxim Shchetynin <maxim@de.ibm.com>,
	linuxppc-dev@ozlabs.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: Re: 1st version of azfs
Date: Mon, 17 Dec 2007 22:24:14 +0100	[thread overview]
Message-ID: <E1J4NRf-0004mg-0G@be1.7eggert.dyndns.org> (raw)
In-Reply-To: 9Btcy-1LS-23@gated-at.bofh.it

Maxim Shchetynin <maxim@de.ibm.com> wrote:

> +config AZ_FS
> +            tristate "AZFS filesystem support"
> +            default m
                       ^
STRONG NACK, I hate digging in the menu tree and hunting for things I
don't need.

> +            help
> +              Non-buffered filesystem for block devices with a gendisk and
> +              with direct_access() method in gendisk->fops.
> +              AZFS does not buffer outgoing traffic and is doing no read
> ahead.
> +              AZFS uses block-size and sector-size provided by block
> device
> +              and gendisk's queue. Though mmap() method is available only
> if
> +              block-size equals to or is greater than system page size.

What is the benefit or intended use of this filesystem? Will your intended
user say "gendisk->fops->direct_access? I wanted to use it all my life"?

AZFZ seems to be an acronym. AirZound File System?
http://globetrotter.de/de/shop/detail.php?mod_nr=ex_35001&GTID=7c553060901a873c5bd29a1846ff39a3a32

       reply	other threads:[~2007-12-17 21:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9Btcy-1LS-23@gated-at.bofh.it>
2007-12-17 21:24 ` Bodo Eggert [this message]
2007-12-17 18:45 1st version of azfs Maxim Shchetynin
  -- strict thread matches above, loose matches on Subject: below --
2007-12-17 18:45 Maxim Shchetynin
2007-12-17 19:17 ` Dave Hansen
2007-12-17 19:28 ` Jan Engelhardt

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=E1J4NRf-0004mg-0G@be1.7eggert.dyndns.org \
    --to=7eggert@gmx.de \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=maxim@de.ibm.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).