All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Nikolay Aleksandrov <nikolay@redhat.com>
Cc: Tadeusz Struk <tadeusz.struk@intel.com>,
	herbert@gondor.apana.org.au, bruce.w.allan@intel.com,
	qat-linux@intel.com, naleksan@redhat.com,
	linux-crypto@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa
Date: Wed, 15 Oct 2014 07:25:45 -0400	[thread overview]
Message-ID: <543E59B9.6060804@redhat.com> (raw)
In-Reply-To: <543E4DFF.9000101@redhat.com>



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 use predefined
>> functions instead.
>>
>> Signed-off-by: Tadeusz Struk <tadeusz.struk@intel.com>
>> ---
>>
>> Tadeusz Struk (2):
>>        crypto: qat - Prevent dma mapping zero length assoc data
>>        crypto: qat - Enforce valid numa configuration
>>
>>
>>   drivers/crypto/qat/qat_common/adf_accel_devices.h |    3 +-
>>   drivers/crypto/qat/qat_common/adf_transport.c     |   12 +++++---
>>   drivers/crypto/qat/qat_common/qat_algs.c          |    7 +++--
>>   drivers/crypto/qat/qat_common/qat_crypto.c        |    8 +++--
>>   drivers/crypto/qat/qat_dh895xcc/adf_admin.c       |    2 +
>>   drivers/crypto/qat/qat_dh895xcc/adf_drv.c         |   32 ++++++++-------------
>>   drivers/crypto/qat/qat_dh895xcc/adf_isr.c         |    2 +
>>   7 files changed, 32 insertions(+), 34 deletions(-)
>>
> 
> 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 <nikolay@redhat.com>

Thanks Nik :)

Reviewed-by: Prarit Bhargava <prarit@redhat.com>

P.

  reply	other threads:[~2014-10-15 11:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14  1:24 [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa Tadeusz Struk
2014-10-14  1:24 ` [PATCH v2 1/2] crypto: qat - Prevent dma mapping zero length assoc data Tadeusz Struk
2014-10-14  1:24 ` [PATCH v2 2/2] crypto: qat - Enforce valid numa configuration Tadeusz Struk
2014-10-14 10:53   ` Prarit Bhargava
2014-10-14 14:50     ` Tadeusz Struk
2014-10-14 15:41       ` Prarit Bhargava
2014-10-14 17:18         ` Tadeusz Struk
2014-10-14 17:27           ` Prarit Bhargava
2014-10-14 17:32             ` Prarit Bhargava
2014-10-15 10:35 ` [PATCH v2 0/2] crypto: qat - Fix for invalid dma mapping and numa Nikolay Aleksandrov
2014-10-15 11:25   ` Prarit Bhargava [this message]
2014-10-15 16:24     ` Tadeusz Struk
2014-10-24 14:45     ` Herbert Xu
2014-11-17 15:43       ` Tadeusz Struk
2014-11-17 16:59         ` Greg KH
2014-11-17 17:20           ` Tadeusz Struk
2014-11-17 18:33             ` Greg KH
2014-12-05 18:34 ` Tadeusz Struk
2014-12-06  6:45   ` Herbert Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=543E59B9.6060804@redhat.com \
    --to=prarit@redhat.com \
    --cc=bruce.w.allan@intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=naleksan@redhat.com \
    --cc=nikolay@redhat.com \
    --cc=qat-linux@intel.com \
    --cc=tadeusz.struk@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.