public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH 0/5] ipc/sem.c: multiple fixes
Date: Mon, 17 Oct 2011 14:43:48 +0200	[thread overview]
Message-ID: <1318855428.4172.16.camel@twins> (raw)
In-Reply-To: <1318684879-1887-1-git-send-email-manfred@colorfullife.com>

On Sat, 2011-10-15 at 15:21 +0200, Manfred Spraul wrote:
> Hi all,
> 
> The wakeup scheme used by semtimedop() does not work as intended on -rt.
> 
> The following series:
> - fixes one bug that I noticed while thinking about a -rt compatible
>   implementation
> - prevents the code from returning to user space due to spurious wakeups.
>   (noticed by Peter Zijlstra)
> - moves private structures from include/linux/sem.h to ipc/sem.c
> - saves some memory if sysvipc is disabled.
> - reworks the wakeup scheme and adds a 2nd wakeup scheme that is based
>   on a completion. For CONFIG_PREEMPT_RT_BASE, this scheme is used.
> 
> What do you think?
> The rework of the wakeup should also help to convert the code to
> using the wake_up_list framework.
> 
> Andrew: Could you replace the patches in -mm with this series?
> I would prefer to keep the current scheme as the default, it's
> ~5% faster (6.5 usec vs. 6.8 usec per wakeup).
> 
> The patches pass checkpatch.pl and I didn't observe any problems
> with my test apps.

For patches 1-4:

Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>

I still need to kick my brain in gear and parse patch 5.

      reply	other threads:[~2011-10-17 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-15 13:21 [PATCH 0/5] ipc/sem.c: multiple fixes Manfred Spraul
2011-10-17 12:43 ` Peter Zijlstra [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=1318855428.4172.16.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@google.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=tglx@linutronix.de \
    /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