[lkml]   [2005]   [Apr]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC] CryptoAPI & Compression
    On Sun, Apr 03, 2005 at 12:22:12PM +0400, Artem B. Bityuckiy wrote:
    > The latter case is possible if the input isn't compressible and it is up
    > to user to detect that handle this situation properly (i.e., just not to
    > compress this). So, IMO, there are no problems here at least for the
    > crypto_comp_pcompress() function.

    Surely that defeats the purpose of pcompress? I thought the whole point
    was to compress as much of the input as possible into the output?

    So 1G into 1G doesn't make sense here. But 1G into 1M does and you
    want to put as much as you can in there. Otherwise we might as well
    delete crypto_comp_pcompress :)
    Visit Openswan at
    Email: Herbert Xu ~{PmV>HI~} <>
    Home Page:
    PGP Key:
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-04-06 13:31    [W:0.019 / U:3.008 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site