Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Waiman Long <llong@redhat.com>
Subject: Re: [PATCH -tip 0/2] locking/rwbase: Two reader optimizations
To:     Davidlohr Bueso <dave@stgolabs.net>, tglx@linutronix.de
Cc:     peterz@infradead.org, mingo@kernel.org, rostedt@goodmis.org,
        bigeasy@linutronix.de, boqun.feng@gmail.com,
        linux-kernel@vger.kernel.org
References: <20210920052031.54220-1-dave@stgolabs.net>
Message-ID: <1676b749-3fca-fa67-03e6-7639ef1f5b33@redhat.com>
Date:   Mon, 20 Sep 2021 17:54:19 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <20210920052031.54220-1-dave@stgolabs.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Precedence: bulk

On 9/20/21 1:20 AM, Davidlohr Bueso wrote:
> Hi,
>
> Patch 1 is a barrier optimization that came up from the reader
> fastpath ordering auditing.
>
> Patch 2 is a resend of the previous broken patch that attempts
> to use wake_q for read_unlock() slowpath.
>
> Tested on v5.15.y-rt. Applies against tip/urgent.
>
> Thanks!
>
> Davidlohr Bueso (2):
>    locking/rwbase: Optimize rwbase_read_trylock
>    locking/rwbase: Lockless reader waking up a writer
>
>   kernel/locking/rtmutex.c   | 19 +++++++++++++------
>   kernel/locking/rwbase_rt.c | 11 +++++++----
>   2 files changed, 20 insertions(+), 10 deletions(-)
>
> --
> 2.26.2
>
Your patches look good to me.

Acked-by: Waiman Long <longman@redhat.com>