linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Maxim Shchetynin <maxim@linux.vnet.ibm.com>
Cc: linux-fsdevel@vger.kernel.org,
	Jan Engelhardt <jengelh@medozas.de>,
	Matthew Wilcox <matthew@wil.cx>,
	linux-kernel@vger.kernel.org
Subject: Re: AZFS file system proposal
Date: Tue, 17 Jun 2008 16:45:26 +0200	[thread overview]
Message-ID: <20080617144526.GA28448@logfs.org> (raw)
In-Reply-To: <20080617160628.79efd2d9@mercedes-benz.boeblingen.de.ibm.com>

On Tue, 17 June 2008 16:06:28 +0200, Maxim Shchetynin wrote:
> > 
> > My personal question when looking at this is: Why not use ext2?  It
> 
> Same reason we don't use ext2 for file system in RAM - we don't need any expensive caching and readahead mechanisms for devices which are as fast as main memory (or almost as fast).

Well, with the '-o xip' option I mentioned below, there is no caching or
readahead.  The direct_access method you use as well was developed for
ext2.  Or rather for xip2fs, another new filesystem.  After some review,
that was shot down and a mount option was added to ext2 instead.

> > appears to me that an ext2 mounted with '-o xip' would solve the same
> > problems.

Jörn

-- 
Homo Sapiens is a goal, not a description.
-- unknown
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-06-17 14:45 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
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 [this message]
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=20080617144526.GA28448@logfs.org \
    --to=joern@logfs.org \
    --cc=jengelh@medozas.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --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;
as well as URLs for NNTP newsgroup(s).