Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp2613255imb; Mon, 4 Mar 2019 09:26:41 -0800 (PST) X-Google-Smtp-Source: APXvYqz0cTo+CGtagegsZqactkNV//n33Su9vOrG1E64L+gHnDfFazUzELK/wcRGtmrAmT6RyUDV X-Received: by 2002:aa7:8b09:: with SMTP id f9mr20961329pfd.168.1551720401085; Mon, 04 Mar 2019 09:26:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551720401; cv=none; d=google.com; s=arc-20160816; b=iLMmUdDlX6RSVXbNtiTQQP4X2AcCm+vxG8KbPwYeEAvNUZkZPiC1SUhoHLxcEzzSQ3 VjLWD91Ib94SYu1xMbghEvMfci05K/g1QQ2fIIZBjCxfHop181dp+wPM67YdrD915UNL tY8nDTke7qOLTY75ZrhmBY32e9UugfGLsWnpnBbcJoXWgKfjBDUVXaMv3030NWYcfyMb ChPgvSfePbSezlkQ+I0bQ727ZqycEvz2NoEj7LwOYrFkrKUKnX06fnBnt5C5Eod198ck 7mmG4bPNnrzVi6nY/eq5GnhSuBAZJCy68pQuKKHbcSXJlIuIrsGn95oQPdrrJNmIYyzE uVOA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=MVbwhV5k9mU56ew2Y2arSjxs1fwMy+zcufQSnk7+V8o=; b=lG7LIiJSH8a2xeHMHjq5P1bTaeBzAJVlWbrqsDM71WWYKFvfb1KuWapYnm/YtRDORN cd0U1IZooibOnYwHowqcmuTSGKp/+b9hyFNIW4OKbtuJxkHt2Kj73PKhkY3VL2N2k2R7 ZlE+9Z1LqhgBy8Hew9jyENzm3fSe82qkQz5NrQ9IeIa4Vqyg/wmpR8v2QLHDCV8jCiNE Vujy5raEA2A/qrsnks/Yjt+qLMp5CqG6H3R+hc2JjtOHqLZYePi7rGYOm8fYb4FwBOvz OgcX9ZROMI+kkQzgW+nJG1icB2vtnKytIVgFci9evR9uGW3cQQX8GKisq8d3Lr8OsC94 p5Og== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n81si5773828pfh.272.2019.03.04.09.26.25; Mon, 04 Mar 2019 09:26:41 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727122AbfCDRZq convert rfc822-to-8bit (ORCPT + 99 others); Mon, 4 Mar 2019 12:25:46 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:41982 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726559AbfCDRZp (ORCPT ); Mon, 4 Mar 2019 12:25:45 -0500 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1h0rLL-0004j1-GK; Mon, 04 Mar 2019 18:25:35 +0100 Date: Mon, 4 Mar 2019 18:25:35 +0100 From: Sebastian Andrzej Siewior To: Julien Grall Cc: Dave Martin , Ard Biesheuvel , linux-arm-kernel , linux-rt-users@vger.kernel.org, Catalin Marinas , Will Deacon , Linux Kernel Mailing List Subject: Re: [RFC PATCH] arm64/fpsimd: Don't disable softirq when touching FPSIMD/SVE state Message-ID: <20190304172535.v5pf7yboii7ayxnb@linutronix.de> References: <20190208165513.8435-1-julien.grall@arm.com> <20190213143029.ad2kzg7vtuo3zpjk@linutronix.de> <20190213153630.GK3567@e103592.cambridge.arm.com> <20190213165227.7ekekkxazhbaqxoe@linutronix.de> <20190214103449.GN3567@e103592.cambridge.arm.com> <32ba7e1e-37ce-c904-15e4-9c908e873479@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: <32ba7e1e-37ce-c904-15e4-9c908e873479@arm.com> User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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