[PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa

2014-10-13 Thread Tadeusz Struk
Hi, These two patches fix invalid (zero length) dma mapping and enforce numa configuration for maximum performance. Change log: v2 - Removed numa node calculation based bus number and use predefined functions instead. Signed-off-by: Tadeusz Struk --- Tadeusz Struk (2): crypto: qat - Preve

Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa

2014-10-15 Thread Nikolay Aleksandrov
On 14/10/14 03:24, Tadeusz Struk wrote: Hi, These two patches fix invalid (zero length) dma mapping and enforce numa configuration for maximum performance. Change log: v2 - Removed numa node calculation based bus number and use predefined functions instead. Signed-off-by: Tadeusz Struk --- Ta

Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa

2014-10-15 Thread Prarit Bhargava
On 10/15/2014 06:35 AM, Nikolay Aleksandrov wrote: > On 14/10/14 03:24, Tadeusz Struk wrote: >> Hi, >> These two patches fix invalid (zero length) dma mapping and >> enforce numa configuration for maximum performance. >> >> Change log: >> v2 - Removed numa node calculation based bus number and us

Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa

2014-10-15 Thread Tadeusz Struk
On 10/15/2014 04:25 AM, Prarit Bhargava wrote: >> I just gave a quick run of these patches and they seem to fix the NUMA issue >> and >> > the 0 length warnings. >> > >> > Tested-by: Nikolay Aleksandrov > Thanks Nik :) > > Reviewed-by: Prarit Bhargava Thank you Nik and Prarit -- To unsubscrib

Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa

2014-10-24 Thread Herbert Xu
On Wed, Oct 15, 2014 at 07:25:45AM -0400, Prarit Bhargava wrote: > > > On 10/15/2014 06:35 AM, Nikolay Aleksandrov wrote: > > On 14/10/14 03:24, Tadeusz Struk wrote: > >> Hi, > >> These two patches fix invalid (zero length) dma mapping and > >> enforce numa configuration for maximum performance.

Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa

2014-11-17 Thread Tadeusz Struk
On 10/24/2014 07:45 AM, Herbert Xu wrote: > On Wed, Oct 15, 2014 at 07:25:45AM -0400, Prarit Bhargava wrote: >> >> >> On 10/15/2014 06:35 AM, Nikolay Aleksandrov wrote: >>> On 14/10/14 03:24, Tadeusz Struk wrote: Hi, These two patches fix invalid (zero length) dma mapping and enforce

Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa

2014-11-17 Thread Greg KH
On Mon, Nov 17, 2014 at 07:43:08AM -0800, Tadeusz Struk wrote: > On 10/24/2014 07:45 AM, Herbert Xu wrote: > > On Wed, Oct 15, 2014 at 07:25:45AM -0400, Prarit Bhargava wrote: > >> > >> > >> On 10/15/2014 06:35 AM, Nikolay Aleksandrov wrote: > >>> On 14/10/14 03:24, Tadeusz Struk wrote: > Hi,

Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa

2014-11-17 Thread Tadeusz Struk
On 11/17/2014 08:59 AM, Greg KH wrote: > Because it showed up in Linus's tree _after_ 3.17.3-rc1 was released? > How can I go back in time? I thought it was already possible, no? :) So will it be in 3.17.4? Thanks, Tadeusz -- To unsubscribe from this list: send the line "unsubscribe linux-crypto

Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa

2014-11-17 Thread Greg KH
On Mon, Nov 17, 2014 at 09:20:34AM -0800, Tadeusz Struk wrote: > On 11/17/2014 08:59 AM, Greg KH wrote: > > Because it showed up in Linus's tree _after_ 3.17.3-rc1 was released? > > How can I go back in time? > > I thought it was already possible, no? :) > So will it be in 3.17.4? Possibly, if I

Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa

2014-12-05 Thread Tadeusz Struk
On 10/13/2014 06:24 PM, Tadeusz Struk wrote: > Hi, > These two patches fix invalid (zero length) dma mapping and > enforce numa configuration for maximum performance. > > Change log: > v2 - Removed numa node calculation based bus number and use predefined > functions instead. > > Signed-off-by: T

Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa

2014-12-05 Thread Herbert Xu
On Fri, Dec 05, 2014 at 10:34:33AM -0800, Tadeusz Struk wrote: > > Looks like these two are not in cryptodev-2.6 yet. > Do you plan to merge it sometime soon or should I generate incremental > patches based on crypto-2.6 instead of cryptodev-2.6 Just generate them on top of all your existing patch