From owner-dev-commits-src-all@freebsd.org Fri Aug 6 09:09:55 2021 Return-Path: Delivered-To: dev-commits-src-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6203665229E; Fri, 6 Aug 2021 09:09:55 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Gh06q1d8Wz3n28; Fri, 6 Aug 2021 09:09:55 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [178.17.145.105]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 198FF260206; Fri, 6 Aug 2021 11:09:54 +0200 (CEST) Subject: Re: git: 09066b98663d - main - ktls: Use the new PNOLOCK flag To: Ian Lepore , Andrew Gallatin , src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org References: <202108052251.175MpwTC090873@gitrepo.freebsd.org> From: Hans Petter Selasky Message-ID: <18ed8e5f-d042-478b-e18c-dd0de7affcae@selasky.org> Date: Fri, 6 Aug 2021 11:09:43 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Gh06q1d8Wz3n28 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: dev-commits-src-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the src repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Aug 2021 09:09:55 -0000 On 8/6/21 1:58 AM, Ian Lepore wrote: > I especially like this solution, it documents explicitly what you're > doing and why. (Earlier I was considering mumbling something about > "there should be a comment to say a sleep-forever is known safe here".) Hi, MPSAFE is the word to use, like with other things related to GIANT? PNOLOCK -> PMPSAFE ?? --HPS