Re: Reiser4 status: benchmarked vs. V3 (and ext3)

From: Yury Umanets (umka_at_namesys.com)
Date: 07/26/03

  • Next message: Andrew Morton: "Re: Debug: sleeping function called from invalid context at include/linux/rwsem.h:43"
    To: Daniel Egger <degger@fhm.edu>
    Date:	26 Jul 2003 11:19:50 +0400
    
    

    On Sat, 2003-07-26 at 05:08, Daniel Egger wrote:
    > Am Fre, 2003-07-25 um 16.39 schrieb Yury Umanets:
    >
    > > Reiser4 has plugin-based architecture. So, anybody is able to write new
    > > block allocator plugin.
    >
    > Cool.

    >
    > > Speaking about possible embedded usage... What kind of embedded devices
    > > do you mean. Reiser4 driver is big enough in size for some of them (for
    > > instance, for mine MPIO MP3 player :))
    >
    > I'm talking about pretty standard ix86 hardware which has embedded like
    > properties such as fanless and motorless use, hardware watchdog, flash
    > memory but only few of the typical limitations like restricted memory
    > (we are using 256 or 512 MB), slow CPU, few connectors.

    >
    > So basically we do have pretty powerful hardware with huge storage and
    > memory and now need a FS which is fast and reliable even on flash
    > memory. JFFS2 is nice but way too slow once one has bigger sizes.

    I think this is more then enough for running reiser4. Reiser4 is a linux
    filesystem first of all, and linux is able to be ran on even worse
    hardware then you have.

    -- 
    We're flying high, we're watching the world passes by...
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Andrew Morton: "Re: Debug: sleeping function called from invalid context at include/linux/rwsem.h:43"

    Relevant Pages

    • Re: Good bye
      ... And if you expect a 5-year useful life for hardware, ... windows machines are as stable/reliable as anything running Linux. ... full processor, memory, RF, IF, audio, and peripheral drivers on board. ...
      (Fedora)
    • Re: High memory
      ... memory and then copy it up above 1MB...but if you want to put ... outside the CPU, memory is seen in a completely different light...this ... 1MB with "real mode memory" labelled on it or anything...the actual memory ... the system bus to actual hardware devices...hence, ...
      (alt.lang.asm)
    • Re: Crashes and the Blue Screen of Death!
      ... but the most common cause is hardware failure. ... The most common cause of this is hardware memory corruption. ... are listed on the Windows 2000 Hardware Compatibility List. ... recommended that all users install them as they become available. ...
      (microsoft.public.win2000.general)
    • Re: The variable bit cpu
      ... > However looking at the big picture the effort to scale fixed bit hardware ... those bits are kept in the opcode rather than in each memory ... And while a *few* applications might need to scale beyond 256 bits, ... And one *big* thing you're missing here is that have a variable-bit ...
      (alt.lang.asm)
    • Re: Strange memory leak in 2.6.x
      ... > identical hardware and simulated disk-io. ... the previous OOM output it shows that it is zone normal that is ... completely out of memory and that highmem zone has lots of free memory. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)