public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Maxim Shchetynin <maxim@linux.vnet.ibm.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: AZFS file system proposal
Date: Mon, 9 Jun 2008 06:55:30 -0600	[thread overview]
Message-ID: <20080609125530.GF30405@parisc-linux.org> (raw)
In-Reply-To: <20080609104650.4f220492@mercedes-benz.boeblingen.de.ibm.com>

On Mon, Jun 09, 2008 at 10:46:50AM +0200, Maxim Shchetynin wrote:
> +config AZ_FS
> +	tristate "AZFS filesystem support"
> +	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.
> +	  It supports mount options (given with -o) bs=x,uid=x,gid=x.
> +	  If block-size (bs) is not specified AZFS uses block-size used
> +	  by block device. Though mmap() method is available only if
> +	  block-size equals to or is greater than system page size.

This is a terrible description.  I can't even suggest better wording
because I don't understand it.  The correct wording would not mention
gendisks, fops or direct_access().  It would tell the user what they
might use it for.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2008-06-09 12:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09  8:46 AZFS file system proposal Maxim Shchetynin
2008-06-09 12:55 ` Matthew Wilcox [this message]
2008-06-10  8:49   ` Maxim Shchetynin
2008-06-10 22:02     ` Jan Engelhardt
2008-06-17  9:06       ` Maxim Shchetynin
2008-06-17  9:35         ` Jan Engelhardt
2008-06-17 10:53           ` Jörn Engel
2008-06-17 14:06             ` Maxim Shchetynin
2008-06-17 14:45               ` Jörn Engel
2008-06-17 11:57           ` Maxim Shchetynin
2008-06-17 14:36             ` Jan Engelhardt
2008-06-17 15:51               ` Jörn Engel
2008-06-18 11:15               ` Maxim Shchetynin
2008-06-18 20:56                 ` Jörn Engel
2008-06-18 11:21               ` Maxim Shchetynin
2008-06-17 15:02 ` Dmitri Vorobiev
2008-06-18 14:01   ` Maxim Shchetynin
2008-06-18 11:27 ` Christoph Hellwig
2008-06-18 14:03   ` Maxim Shchetynin
  -- strict thread matches above, loose matches on Subject: below --
2008-06-18 14:06 Maxim Shchetynin
2008-07-01 14:59 ` Arnd Bergmann
2008-07-07 15:39   ` Maxim Shchetynin
2008-07-08 14:42     ` Arnd Bergmann
2008-07-09  6:48       ` Benjamin Herrenschmidt
2008-07-09  8:58   ` Benjamin Herrenschmidt
2008-07-09  9:14     ` Maxim Shchetynin
2008-07-09  9:23       ` Benjamin Herrenschmidt
2008-07-09 10:58         ` Maxim Shchetynin

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=20080609125530.GF30405@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxim@linux.vnet.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