[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190304172535.v5pf7yboii7ayxnb@linutronix.de>
Date: Mon, 4 Mar 2019 18:25:35 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Julien Grall <julien.grall@....com>
Cc: Dave Martin <Dave.Martin@....com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-rt-users@...r.kernel.org,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] arm64/fpsimd: Don't disable softirq when touching
FPSIMD/SVE state
On 2019-02-18 15:07:51 [+0000], Julien Grall wrote:
> Hi,
Hi,
> > Wouldn't this arbitrarily increase softirq latency? Unconditionally
> > forbidding SIMD in softirq might make more sense. It depends on how
> > important the use cases are...
It would increase the softirq latency but the question is how bad would
it be. It would continue once the SIMD section is done.
If you allow it but made it impossible to use (and use the software
fallback) then it would slow down the processing. So…
> Looking at the commit message from cb84d11e1625 "arm64: neon: Remove support
> for nested or hardirq kernel-mode NEON", one of the use case for crypto in
> softirq is certain mac80211 drivers.
>
> Is there any other use case for use crypto in softirqs?
mac80211 does it for some wifi drivers. There used to be IPsec but I
*think* this moved to the "parallel processing kthread".
During my FPU rework on x86 I didn't find anything that does the
processing in softirq (on my machine) so I hacked something so that I
could test that I didn't break anything…
> Cheers,
>
Sebastian
Powered by blists - more mailing lists