Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp2587444pxu; Fri, 18 Dec 2020 18:07:07 -0800 (PST) X-Google-Smtp-Source: ABdhPJyfMf72kybSWlC+hOx2SXC4ctb6rAHcsZ3zwjdwPsji9HsLlLa6MKBMAFuhmA9kcrO7SbuZ X-Received: by 2002:a50:b224:: with SMTP id o33mr7281164edd.21.1608343627306; Fri, 18 Dec 2020 18:07:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1608343627; cv=none; d=google.com; s=arc-20160816; b=OnjNqiPLIiFQ5wQxenApTCfyzlkzhTJUkArNkBckTeW/Uq14avmN2wj7KuXmf3k0WR WJoGlGyJ+gC95PD1qeCRzNNbwch2W37LR17pIv7s+fIsphG5l4upEmuaCB3AShBRg641 EtpkqcAJGWDoK869JSp5BKViw3XidXd0EdF/K/BG3tVNy5YSNi/T/WX4aYyw97blXUDm hg5s6jfIyx5kKaMkZpOSJ4SJ7moDU5tgZxpD9xLP1/LfgCVVZDVNVGa3y1asHybed+xP wmHf0axu/zkdLaY1sS9qTJ2YvkaKQIwKTu1Mu+GicfOmungUYs8+Tu/Ujq9kl2phddwD 91Rg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=Ko9VmbYjUH/WoeWTm9IKPmipThMQa8DwnYkyL7Bjnyw=; b=Bi35Va4iZpgcIQkH3BD6T1HjxhXYgdeXcVPvPxi3PQRsd51myMHhP3Wdy9a8kSSUYH eAMDndnpSt2ByUowz89jDJ71X6gV2ECwkyv0zrRZerMXpcWYQWaVAeHpHWU/8y6njOCg V37hOBHPI7fk2lpzGQV6sXu3JhhcpyR14Kr56hZVUU37Ck2LwX026m6rmOAIW/c7sivZ 5Yub8dwGcgcNy4LYv6jd/u9qQi00T5bHtqw6IqqMXsYHYDTOSw+vmZTR7NsrjlhW6Fmh n13/HItkspkmW9jsdB7S2pd+TXX+5QcSCwaBT5fwMQK3zBILwRGxdxSx0xtzRP0pQtkL bYYQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id hr14si5106913ejc.396.2020.12.18.18.06.41; Fri, 18 Dec 2020 18:07:07 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725966AbgLSCFh (ORCPT + 99 others); Fri, 18 Dec 2020 21:05:37 -0500 Received: from helcar.hmeau.com ([216.24.177.18]:41518 "EHLO fornost.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725940AbgLSCFh (ORCPT ); Fri, 18 Dec 2020 21:05:37 -0500 Received: from [192.168.103.7] (helo=gwarestrin.arnor.me.apana.org.au) by fornost.hmeau.com with smtp (Exim 4.92 #5 (Debian)) id 1kqRbX-00054x-AV; Sat, 19 Dec 2020 13:04:20 +1100 Received: by gwarestrin.arnor.me.apana.org.au (sSMTP sendmail emulation); Sat, 19 Dec 2020 13:04:33 +1100 Date: Sat, 19 Dec 2020 13:04:33 +1100 From: Herbert Xu To: Ard Biesheuvel Cc: linux-crypto@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Dave Martin , Mark Brown , Eric Biggers , Will Deacon , Catalin Marinas , Thomas Gleixner , Peter Zijlstra , Sebastian Andrzej Siewior , Ingo Molnar Subject: Re: [RFC PATCH 0/5] running kernel mode SIMD with softirqs disabled Message-ID: <20201219020433.GA11077@gondor.apana.org.au> References: <20201218170106.23280-1-ardb@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201218170106.23280-1-ardb@kernel.org> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Fri, Dec 18, 2020 at 06:01:01PM +0100, Ard Biesheuvel wrote: > > Questions: > - what did I miss or break horribly? > - does any of this matter for RT? AIUI, RT runs softirqs from a dedicated > kthread, so I don't think it cares. > - what would be a reasonable upper bound to keep softirqs disabled? I suppose > 100s of cycles or less is overkill, but I'm not sure how to derive a better > answer. > - could we do the same on x86, now that kernel_fpu_begin/end is no longer > expensive? If this approach works not only would it allow us to support the synchronous users better, it would also allow us to remove loads of cruft in the Crypto API that exist solely to support these SIMD code paths. So I eagerly await the assessment of the scheduler/RT folks on this approach. Thanks, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt