mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] start using spin primitives in sched and locking
Date: Fri, 1 Sep 2017 14:01:23 +1000	[thread overview]
Message-ID: <20170901140123.56c5abb2@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20170820092502.6812-1-npiggin@gmail.com>

Hi guys,

Any thoughts on these?

Thanks,
Nick

On Sun, 20 Aug 2017 19:25:00 +1000
Nicholas Piggin <npiggin@gmail.com> wrote:

> Nicholas Piggin (2):
>   locking: Use spin primitives for busy loops
>   sched/idle: Use spin loop primitives for polling idle
> 
>  include/linux/bit_spinlock.h        |  5 ++---
>  include/linux/seqlock.h             |  9 ++++-----
>  kernel/locking/mcs_spinlock.h       |  6 ++----
>  kernel/locking/mutex.c              | 10 ++++++++--
>  kernel/locking/osq_lock.c           | 17 +++++++++++++----
>  kernel/locking/qrwlock.c            | 11 ++++++++---
>  kernel/locking/qspinlock.c          | 14 ++++++++++----
>  kernel/locking/qspinlock_paravirt.h | 16 ++++++++++++----
>  kernel/locking/rwsem-xadd.c         |  9 +++++++--
>  kernel/sched/idle.c                 |  7 ++++++-
>  10 files changed, 72 insertions(+), 32 deletions(-)
> 

      parent reply	other threads:[~2017-09-01  4:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-20  9:25 Nicholas Piggin
2017-08-20  9:25 ` [PATCH 1/2] locking: Use spin primitives for busy loops Nicholas Piggin
2017-09-01 12:23   ` Peter Zijlstra
2017-09-06  0:08     ` Nicholas Piggin
2017-08-20  9:25 ` [PATCH 2/2] sched/idle: Use spin loop primitives for polling idle Nicholas Piggin
2017-09-01 12:24   ` Peter Zijlstra
2017-09-06  0:15     ` Nicholas Piggin
2017-09-01  4:01 ` Nicholas Piggin [this message]

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=20170901140123.56c5abb2@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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
Powered by JetHome