[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MW5PR84MB1842141A89926F7E28E4F752AB259@MW5PR84MB1842.NAMPRD84.PROD.OUTLOOK.COM>
Date: Thu, 13 Oct 2022 21:50:52 +0000
From: "Elliott, Robert (Servers)" <elliott@....com>
To: "Jason A. Donenfeld" <Jason@...c4.com>
CC: "herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>,
"davem@...emloft.net" <davem@...emloft.net>,
"tim.c.chen@...ux.intel.com" <tim.c.chen@...ux.intel.com>,
"ap420073@...il.com" <ap420073@...il.com>,
"ardb@...nel.org" <ardb@...nel.org>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v2 04/19] crypto: x86/sha - limit FPU preemption
> > +#define FPU_BYTES 4096U /* avoid kernel_fpu_begin/end scheduler/rcu stalls
> */
>
> Declare this inside the function it's used as an untyped enum, and give
> it a better name, like BYTES_PER_FPU.
I agree that's a better name, and will use something like that depending
on how other discussions go. I was trying to keep it as a one-line change
within 80 characters, expecting some churn before it's finalized.
Powered by blists - more mailing lists