17 Oct, 2007

1 commit

  • Since CONFIG_RAMFS is currently hard-selected to "y", and since
    Documentation/filesystems/ramfs-rootfs-initramfs.txt reads as follows:

    "The amount of code required to implement ramfs is tiny, because all the
    work is done by the existing Linux caching infrastructure. Basically,
    you're mounting the disk cache as a filesystem. Because of this, ramfs is
    not an optional component removable via menuconfig, since there would be
    negligible space savings."

    It seems pointless to leave this as a Kconfig entry.

    Signed-off-by: Robert P. J. Day
    Cc: Al Viro
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Robert P. J. Day
     

07 Jan, 2006

1 commit

  • The attached patch makes ramfs support shared-writable mmaps by:

    (1) Attempting to perform a contiguous block allocation to the requested size
    when truncate attempts to increase the file from zero size, such as
    happens when:

    fd = shm_open("/file/on/ramfs", ...):
    ftruncate(fd, size_requested);
    addr = mmap(NULL, subsize, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_SHARED,
    fd, offset);

    (2) Permitting any shared-writable mapping over any contiguous set of extant
    pages. get_unmapped_area() will return the address into the actual ramfs
    pages. The mapping may start anywhere and be of any size, but may not go
    over the end of file. Multiple mappings may overlap in any way.

    (3) Not permitting a file to be shrunk if it would truncate any shared
    mappings (private mappings are copied).

    Thus this patch provides support for POSIX shared memory on NOMMU kernels,
    with certain limitations such as there being a large enough block of pages
    available to support the allocation and it only working on directly mappable
    filesystems.

    Signed-off-by: David Howells
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Howells
     

17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds