From: Sven Auhagen <sven.auhagen@voleatech.de>
To: linux-crypto@vger.kernel.org
Subject: [PATCH 1/1] inside-secure irq balance
Date: Wed, 8 Jul 2020 17:08:44 +0200 [thread overview]
Message-ID: <20200708150844.2626m3pgdo5oidzm@SvensMacBookAir.sven.lan> (raw)
Balance the irqs of the inside secure driver over all
available cpus.
Currently all interrupts are handled by the first CPU.
From my testing with IPSec AES-GCM 256
on my MCbin with 4 Cores I get a 50% speed increase:
Before the patch: 99.73 Kpps
With the patch: 151.25 Kpps
Signed-off-by: Sven Auhagen <sven.auhagen@voleatech.de>
---
drivers/crypto/inside-secure/safexcel.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/crypto/inside-secure/safexcel.c b/drivers/crypto/inside-secure/safexcel.c
index 2cb53fbae841..f206084be08e 100644
--- a/drivers/crypto/inside-secure/safexcel.c
+++ b/drivers/crypto/inside-secure/safexcel.c
@@ -1135,11 +1135,12 @@ static irqreturn_t safexcel_irq_ring_thread(int irq, void *data)
static int safexcel_request_ring_irq(void *pdev, int irqid,
int is_pci_dev,
+ int ring_id,
irq_handler_t handler,
irq_handler_t threaded_handler,
struct safexcel_ring_irq_data *ring_irq_priv)
{
- int ret, irq;
+ int ret, irq, cpu;
struct device *dev;
if (IS_ENABLED(CONFIG_PCI) && is_pci_dev) {
@@ -1177,6 +1178,10 @@ static int safexcel_request_ring_irq(void *pdev, int irqid,
return ret;
}
+ // Set affinity
+ cpu = ring_id % num_online_cpus();
+ irq_set_affinity_hint(irq, get_cpu_mask(cpu));
+
return irq;
}
@@ -1611,6 +1616,7 @@ static int safexcel_probe_generic(void *pdev,
irq = safexcel_request_ring_irq(pdev,
EIP197_IRQ_NUMBER(i, is_pci_dev),
is_pci_dev,
+ i,
safexcel_irq_ring,
safexcel_irq_ring_thread,
ring_irq);
--
2.20.1
next reply other threads:[~2020-07-08 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 15:08 Sven Auhagen [this message]
2020-07-16 7:21 ` [PATCH 1/1] inside-secure irq balance Herbert Xu
2020-07-16 8:44 ` Van Leeuwen, Pascal
2020-07-16 9:21 ` Sven Auhagen
2020-07-16 12:04 ` Herbert Xu
2020-07-17 5:01 ` Sven Auhagen
2020-07-17 5:20 ` Herbert Xu
2020-07-17 6:35 ` Sven Auhagen
2020-07-17 6:57 ` Herbert Xu
2020-07-17 7:53 ` Sven Auhagen
2020-07-17 8:56 ` Van Leeuwen, Pascal
2020-07-17 13:50 ` Herbert Xu
2020-07-16 10:31 ` Sven Auhagen
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=20200708150844.2626m3pgdo5oidzm@SvensMacBookAir.sven.lan \
--to=sven.auhagen@voleatech.de \
--cc=linux-crypto@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).