linux-kernel - Re: [PATCH] doc:lock: remove reference to clever use of read-write lock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190831084344.6fd7c039@lwn.net>
Date:   Sat, 31 Aug 2019 08:43:44 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Federico Vaga <federico.vaga@...a.pv.it>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
        linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH] doc:lock: remove reference to clever use of read-write
 lock

On Sat, 31 Aug 2019 15:41:16 +0200
Federico Vaga <federico.vaga@...a.pv.it> wrote:

>  several CPU's and you want to use spinlocks you can potentially use
> -cheaper versions of the spinlocks. IFF you know that the spinlocks are
> +cheaper versions of the spinlocks. If you know that the spinlocks are
>  never used in interrupt handlers, you can use the non-irq versions::

I suspect that was not actually a typo; "iff" is a way for the
mathematically inclined to say "if and only if".

jon