Re: [RFC PATCH v1 0/1] *** crypto: AF_ALG: add compression support ***

2017-04-20 Thread abed mohammad kamaluddin
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 >>

Re: [RFC PATCH v1 0/1] *** crypto: AF_ALG: add compression support ***

2017-04-20 Thread Herbert Xu
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. > >

Re: [RFC PATCH v1 0/1] *** crypto: AF_ALG: add compression support ***

2017-04-20 Thread abed mohammad kamaluddin
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

Re: [RFC PATCH v1 0/1] *** crypto: AF_ALG: add compression support ***

2017-04-14 Thread Herbert Xu
On Fri, Apr 14, 2017 at 12:04:53AM +0530, Abed Kamaluddin wrote: > Hi Herbert, > > This patch adds compression support to the AF_ALG interface exported by the > kernel crypto API. By extending AF_ALG, all compression algorithms of types > scomp and acomp, which the kernel crypto API allows