Hi Herbert, >> > I think we should convert ipcomp over to the new interface first >> > in order to make sure that we don't need to change the interface >> > which would be hard to do once we export it to user-space. >> >> Would it be acceptable if we export an algif interface using alg_type_compress, > > No we're not going to export an obsolete interface. > Are there any deficiencies expected in the acomp interface for use with ipcomp? One issue mentioned earlier on the lists was that the interface might require tweaks for piecemeal decompression. Has this been taken up? We identified few issues when using acomp with user-space zlib for file compression. If the the interface is tweaked keeping those use-cases in mind apart from the existing kernel apps (zswap/ipcomp/zram), the hardware algorithms can be utilized using the algif framework. Thanks Abed On Thu, Apr 20, 2017 at 1:30 PM, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote: > On Thu, Apr 20, 2017 at 12:39:58PM +0530, abed mohammad kamaluddin wrote: >> Hi Herbert, >> >> > I think we should convert ipcomp over to the new interface first >> > in order to make sure that we don't need to change the interface >> > which would be hard to do once we export it to user-space. >> >> Would it be acceptable if we export an algif interface using alg_type_compress, >> which is being used by ipcomp currently? We would like to use our zip >> device from >> userspace through this interface. > > No we're not going to export an obsolete interface. > > Cheers, > -- > Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> > Home Page: http://gondor.apana.org.au/~herbert/ > PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt