[lkml]   [2003]   [Jul]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] cryptoloop
    Chris Friesen wrote:
    > Jari Ruusu wrote:
    > > Because loop-AES attempts to be compatible with structures in loop.h by not
    > > modifying loop.h at all. This is what the "no kernel sources patched or
    > > replaced" means. Breakage in loop.h breaks loop-AES, and I have to clean the
    > > mess.
    > We're in a development stream. It is kind of expected that in-kernel
    > APIs may change if the developers feel it will lead to some improvement.
    > This sucks for people that are trying to track those APIs with
    > out-of-kernel patches, but its a fact of life.

    I know. I already have to deal with API breakages.

    Changing transfer function prototype may be a tiny speed improvement for one
    implementation that happens to use unoptimal API, but at same time be tiny
    speed degration to other implementations that use more saner APIs. I am
    unhappy with that change, because I happen to maintain four such transfers
    that would be subject to tiny speed degration.

    Jari Ruusu <>

    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-03-22 13:46    [W:0.042 / U:11.864 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site