From: Tero Kristo <t-kristo@ti.com>
To: <herbert@gondor.apana.org.au>, <lokeshvutla@ti.com>,
<davem@davemloft.net>, <linux-crypto@vger.kernel.org>,
<linux-omap@vger.kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 8/8] crypto: omap-sham: shrink the internal buffer size
Date: Mon, 19 Sep 2016 18:22:19 +0300 [thread overview]
Message-ID: <1474298539-23897-9-git-send-email-t-kristo@ti.com> (raw)
In-Reply-To: <1474298539-23897-1-git-send-email-t-kristo@ti.com>
The current internal buffer size is way too large for crypto core, so
shrink it to be smaller. This makes the buffer to fit into the space
reserved for the export/import buffers also.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
---
drivers/crypto/omap-sham.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c
index 8eefd79..d0b16e5 100644
--- a/drivers/crypto/omap-sham.c
+++ b/drivers/crypto/omap-sham.c
@@ -135,7 +135,7 @@
#define OMAP_ALIGN_MASK (sizeof(u32)-1)
#define OMAP_ALIGNED __attribute__((aligned(sizeof(u32))))
-#define BUFLEN PAGE_SIZE
+#define BUFLEN SHA512_BLOCK_SIZE
#define OMAP_SHA_DMA_THRESHOLD 256
struct omap_sham_dev;
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Tero Kristo <t-kristo@ti.com>
To: herbert@gondor.apana.org.au, lokeshvutla@ti.com,
davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 8/8] crypto: omap-sham: shrink the internal buffer size
Date: Mon, 19 Sep 2016 18:22:19 +0300 [thread overview]
Message-ID: <1474298539-23897-9-git-send-email-t-kristo@ti.com> (raw)
In-Reply-To: <1474298539-23897-1-git-send-email-t-kristo@ti.com>
The current internal buffer size is way too large for crypto core, so
shrink it to be smaller. This makes the buffer to fit into the space
reserved for the export/import buffers also.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
---
drivers/crypto/omap-sham.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c
index 8eefd79..d0b16e5 100644
--- a/drivers/crypto/omap-sham.c
+++ b/drivers/crypto/omap-sham.c
@@ -135,7 +135,7 @@
#define OMAP_ALIGN_MASK (sizeof(u32)-1)
#define OMAP_ALIGNED __attribute__((aligned(sizeof(u32))))
-#define BUFLEN PAGE_SIZE
+#define BUFLEN SHA512_BLOCK_SIZE
#define OMAP_SHA_DMA_THRESHOLD 256
struct omap_sham_dev;
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 8/8] crypto: omap-sham: shrink the internal buffer size
Date: Mon, 19 Sep 2016 18:22:19 +0300 [thread overview]
Message-ID: <1474298539-23897-9-git-send-email-t-kristo@ti.com> (raw)
In-Reply-To: <1474298539-23897-1-git-send-email-t-kristo@ti.com>
The current internal buffer size is way too large for crypto core, so
shrink it to be smaller. This makes the buffer to fit into the space
reserved for the export/import buffers also.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
---
drivers/crypto/omap-sham.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c
index 8eefd79..d0b16e5 100644
--- a/drivers/crypto/omap-sham.c
+++ b/drivers/crypto/omap-sham.c
@@ -135,7 +135,7 @@
#define OMAP_ALIGN_MASK (sizeof(u32)-1)
#define OMAP_ALIGNED __attribute__((aligned(sizeof(u32))))
-#define BUFLEN PAGE_SIZE
+#define BUFLEN SHA512_BLOCK_SIZE
#define OMAP_SHA_DMA_THRESHOLD 256
struct omap_sham_dev;
--
1.9.1
next prev parent reply other threads:[~2016-09-19 15:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 15:22 [PATCH 0/8] crypto: omap-sham: convert to sg based data engine Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` [PATCH 1/8] crypto: omap-sham: add context export/import stubs Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` [PATCH 2/8] crypto: omap-sham: align algorithms on word offset Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` [PATCH 3/8] crypto: omap-sham: rename sgl to sgl_tmp for deprecation Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` [PATCH 4/8] crypto: omap-sham: add support functions for sg based data handling Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` [PATCH 5/8] crypto: omap-sham: change the DMA threshold value to a define Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` [PATCH 6/8] crypto: omap-sham: convert driver logic to use sgs for data xmit Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` [PATCH 7/8] crypto: omap-sham: add support for export/import Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-19 15:22 ` Tero Kristo [this message]
2016-09-19 15:22 ` [PATCH 8/8] crypto: omap-sham: shrink the internal buffer size Tero Kristo
2016-09-19 15:22 ` Tero Kristo
2016-09-22 10:46 ` [PATCH 0/8] crypto: omap-sham: convert to sg based data engine Herbert Xu
2016-09-22 10:46 ` 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=1474298539-23897-9-git-send-email-t-kristo@ti.com \
--to=t-kristo@ti.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.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.