Re: [PATCH] ramfs fixes

From: Juan J. Quintela (quintela@fi.udc.es)
Date: Sat Jun 17 2000 - 10:15:02 EDT

  • Next message: Davidovac Zoran: "Re: aic7xxx AIC7770 kernel panic:unrecoverable BRKADRINT"

    >>>>> "al" == Alexander Viro <aviro@redhat.com> writes:

    Hi

    al> * adds a new method to address_space_operations: void detach_page(page).
    al> Meaning: do all work necessary to make page droppable. For block-based
    al> filesystems it's block_destroy_buffers(). For ramfs - ClearPageDirty().
    al> It is used by truncate_complete_page() and truncate_all_inode_pages() -
    al> i.e. whenever we are getting rid of a page due to truncate() or final
    al> iput() after unlink().

    Al, do you see any problem to my previous patch to the list about
    including ClearPageDirty(page) in remove_inode_page()???

    The reason to put that is that we need to call that function for all
    the fs when we are truncating a file, and each time more fs have the
    dirty bit set. Actually the Ramfs and the swap, but I have almost
    finished a patch for the deferred_file_write of file mmaped patches
    from swap_out. I sent a WIP version of this patch also to the list
    (the deferred code is not ready for inclusion yet).

    Later, Juan.

    PD. You can get the patches from:

    The one to set the ClearPage Dirty.

    http://carpanta.dc.fi.udc.es/~quintela/kernel/2.4.0-test1-ac19/dirty_buffers_01.patch

    The deferred file write one:

    http://carpanta.dc.fi.udc.es/~quintela/kernel/2.4.0-test1-ac10/defered_write_01.patch

    This one is a proof of concept only implementation, but I would like
    to hear comments.

    -- 
    In theory, practice and theory are the same, but in practice they 
    are different -- Larry McVoy
    

    - 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 Jun 17 2000 - 10:20:02 EDT