mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Tim Chen <tim.c.chen@linux.intel.com>,
	huang ying <huang.ying.caritas@gmail.com>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH-tip v6 01/20] locking/rwsem: Prevent decrement of reader count before increment
Date: Sun, 28 Apr 2019 15:40:01 -0400	[thread overview]
Message-ID: <d251f785-407e-d63f-0591-de6251f6b14f@redhat.com> (raw)
In-Reply-To: <CAHk-=wgGN9KKCW8dii=nXwKQdu2N5AOMrVdS5qJvZAPOTvwHjA@mail.gmail.com>

On 4/28/19 1:59 PM, Linus Torvalds wrote:
> On Sun, Apr 28, 2019 at 10:41 AM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>> It's the *first* loop that you could play games with, because you hold
>> the lock, and the list is stable during that loop. So the *first* loop
>> could just walk the list, and then do one list splitting operation
>> instead of doing that "list_move_tail()" thing for each entry.
> .. having looked at that, I would suggest against it.
>
> I _think_ this short and sweet code snippet might just work fine for
> the first loop:
>
>         list_for_each_entry(waiter, &sem->wait_list, list) {
>                 if (waiter->type == RWSEM_WAITING_FOR_WRITE)
>                         break;
>                 woken++;
>         }
>         list_cut_before(&wlist, &sem->wait_list, waiter);
>
> and if it *does* work it would be both smaller and more efficient. But
> it looks a bit too subtle to my taste. Somebody would need to go
> through that with a fine comb, and double-check that it gets the
> "whole list" case right, for example.
>
> So the "phase 1" loop could be perhaps simplified to the above cute things.
>
> But the "phase 2" loop absolutely has to be changed to use
> list_for_each_entry_safe().
>
>                Linus

You are right. Thanks for checking my code. I will make the necessary
change.

Cheers,
Longman


  reply	other threads:[~2019-04-28 19:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28 15:57 [PATCH-tip v6 00/20] locking/rwsem: Rwsem rearchitecture part 2 Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 01/20] locking/rwsem: Prevent decrement of reader count before increment Waiman Long
2019-04-28 16:07   ` Waiman Long
2019-04-28 17:41   ` Linus Torvalds
2019-04-28 17:59     ` Linus Torvalds
2019-04-28 19:40       ` Waiman Long [this message]
     [not found]   ` <20190428203916.E1AA6206A3@mail.kernel.org>
2019-04-28 20:47     ` Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 02/20] locking/rwsem: Make owner available even if !CONFIG_RWSEM_SPIN_ON_OWNER Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 03/20] locking/rwsem: Remove rwsem_wake() wakeup optimization Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 04/20] locking/rwsem: Implement a new locking scheme Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 05/20] locking/rwsem: Merge rwsem.h and rwsem-xadd.c into rwsem.c Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 06/20] locking/rwsem: Code cleanup after files merging Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 07/20] locking/rwsem: Make rwsem_spin_on_owner() return owner state Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 08/20] locking/rwsem: Implement lock handoff to prevent lock starvation Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 09/20] locking/rwsem: Always release wait_lock before waking up tasks Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 10/20] locking/rwsem: More optimal RT task handling of null owner Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 11/20] locking/rwsem: Wake up almost all readers in wait queue Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 12/20] locking/rwsem: Clarify usage of owner's nonspinaable bit Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 13/20] locking/rwsem: Enable readers spinning on writer Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 14/20] locking/rwsem: Enable time-based spinning on reader-owned rwsem Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 15/20] locking/rwsem: Adaptive disabling of reader optimistic spinning Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 16/20] locking/rwsem: Add more rwsem owner access helpers Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 17/20] locking/rwsem: Guard against making count negative Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 18/20] locking/rwsem: Merge owner into count on x86-64 Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 19/20] locking/rwsem: Remove redundant computation of writer lock word Waiman Long
2019-04-28 15:57 ` [PATCH-tip v6 20/20] locking/rwsem: Disable preemption in down_read*() if owner in count Waiman Long

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d251f785-407e-d63f-0591-de6251f6b14f@redhat.com \
    --to=longman@redhat.com \
    --cc=bp@alien8.de \
    --cc=dave@stgolabs.net \
    --cc=hpa@zytor.com \
    --cc=huang.ying.caritas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=will.deacon@arm.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®