lkml.org 
[lkml]   [2007]   [Apr]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: Back to the future.
    Date
    Am Freitag, 27. April 2007 12:12 schrieb Pekka J Enberg:
    > I am talking about snapshot_system() here. It's not given that the
    > filesystems need to be read-only (you can snapshot them too). The benefit
    > here is that you can do whatever you want with the snapshot (encrypt,
    > compress, send over the network)  and have a clean well-defined interface
    > in the kernel. In addition, aborting the snapshot is simpler, simply
    > munmap() the snapshot.

    But is that worth the trade off?

    > The problem with writing in the kernel is obvious: we need to add new code
    > to the kernel for compression, encryption, and userspace interaction
    > (graphical progress bar) that are important for user experience.

    The kernel can already do compression and encryption.

    Regards
    Oliver
    -
    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/

    \
     
     \ /
      Last update: 2007-04-27 21:17    [W:0.021 / U:0.776 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site