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;
Date:   Fri, 15 Nov 2019 18:14:50 +0100
From:   Juri Lelli <juri.lelli@redhat.com>
To:     Peter Zijlstra <peterz@infradead.org>
Cc:     mingo@kernel.org, will@kernel.org, oleg@redhat.com,
        tglx@linutronix.de, linux-kernel@vger.kernel.org,
        bigeasy@linutronix.de, williams@redhat.com, bristot@redhat.com,
        longman@redhat.com, dave@stgolabs.net, jack@suse.com
Subject: Re: [PATCH 0/5] locking: Percpu-rwsem rewrite
Message-ID: <20191115171450.GJ19129@localhost.localdomain>
References: <20191113102115.116470462@infradead.org>
MIME-Version: 1.0
In-Reply-To: <20191113102115.116470462@infradead.org>
User-Agent: Mutt/1.11.3 (2019-02-01)
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi,

On 13/11/19 11:21, Peter Zijlstra wrote:
> Yet another version of the percpu-rwsem rewrite..
>=20
> This one (ab)uses the waitqueue in an entirely different and unique way, =
but no
> longer shares it like it did. It retains the use of rcuwait for the
> writer-waiting-for-readers-to-complete condition.
>=20
> This one should be FIFO fair with writer-stealing.
>=20
> It seems to pass locktorture torture_type=3Dpercpu_rwsem_lock. But as alw=
ays,
> this stuff is tricky, please look carefully.

Backported this series to v5.2.21-rt13.

locktorture looks good (running for several hours) and DEBUG_LOCKS splat
[1] not reproducible anymore.

Tested-by: Juri Lelli <juri.lelli@redhat.com>

Thanks!

Juri

1 - https://lore.kernel.org/lkml/20190326093421.GA29508@localhost.localdoma=
in/