Re: Really Simple File System versus raw disk I/O

From: Paul Barton-Davis (pbd@Op.Net)
Date: Sat Apr 01 2000 - 17:56:22 EST

  • Next message: Stephen C. Tweedie: "Re: block_dev.c not backward compatible with 2.2.15 APIs"

    >Seriously, if you create an ext2 filesystem and make one large file
    >on it, you get something nice and big, allocated in 8MB or larger
    >contiguous chunks, which you can seek, read and write into at your
    >leisure. What advantage is there in actually denying the user
    >extra functionality? There's nothing to _require_ the application
    >to truncate the big contiguous file if it doesn't need to under
    >any normal filesystem.

    My point was to be able to create more than one file, and to guarantee
    their contiguousness. If I try to do that on ext2, I have to do it right
    after the filesystem is created, and I have to prevent any other files
    from ever being created there.

    But I take your point. More than that, I use ext2 right now. I'm just
    trying to give myself the maximum breathing room when it comes to disk
    i/o, and wondered if a "rawfs" made any sense.

    --p

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/



    This archive was generated by hypermail 2b29 : Sat Apr 01 2000 - 18:00:28 EST