public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Oleg Nesterov <oleg@redhat.com>,
	Paul McKenney <paulmck@linux.vnet.ibm.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] sched, wait: Make the __wait_event*() interface more friendly
Date: Tue, 1 Oct 2013 08:39:54 +0200	[thread overview]
Message-ID: <20131001063954.GA19111@gmail.com> (raw)
In-Reply-To: <20130930152625.131613711@infradead.org>


* Peter Zijlstra <peterz@infradead.org> wrote:

> Change all __wait_event*() implementations to match the corresponding
> wait_event*() signature for convenience.
> 
> In particular this does away with the weird 'ret' logic. Since there
> are __wait_event*() users this requires we update them too.
> 
> Signed-off-by: Peter Zijlstra <peterz@infradead.org>
> ---
>  arch/mips/kernel/rtlx.c         |   19 +++---
>  include/linux/tty.h             |   10 +--
>  include/linux/wait.h            |  113 +++++++++++++++++++---------------------
>  net/irda/af_irda.c              |    5 -
>  net/netfilter/ipvs/ip_vs_sync.c |    7 --
>  5 files changed, 73 insertions(+), 81 deletions(-)

Since now everyone seems to agree about this series, and since this 
particular patch changes generated code it would be really nice to split 
it into about ten per interface patches:

  - __wait_event_interruptible()
  - __wait_event_interruptible_timeout()
  - __wait_event_interruptible_exclusive()
  - __wait_event_interruptible_lock_irq()
  - __wait_event_interruptible_tty()
  - __wait_event()
  - __wait_event_timeout()
  - __wait_event_killable()
  - __wait_event_interruptible_lock_irq_timeout()

The changes seem to be mostly isolated, they are even in separate patch 
hunks most of the time making a splitup relatively easy - with a handful 
of semantic interdependencies.

There's very little downside to doing it the split-up way, and there's a 
lot of bisection and bug review upside, should any of these changes prove 
problematic...

Thanks,

	Ingo

  reply	other threads:[~2013-10-01  6:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 15:22 [PATCH 0/6] sched, wait: Collapse __wait_event macros -v4 Peter Zijlstra
2013-09-30 15:22 ` [PATCH 1/6] sched, wait: Make the signal_pending() checks consistent Peter Zijlstra
2013-09-30 15:22 ` [PATCH 2/6] sched, wait: Change timeout logic Peter Zijlstra
2013-09-30 15:48   ` Linus Torvalds
2013-09-30 16:09     ` Peter Zijlstra
2013-09-30 15:22 ` [PATCH 3/6] sched, wait: Change the wait_exclusive control flow Peter Zijlstra
2013-09-30 15:22 ` [PATCH 4/6] sched, wait: Collapse __wait_event macros Peter Zijlstra
2013-09-30 15:22 ` [PATCH 5/6] sched, wait: Also use ___wait_event() for __wait_event_hrtimeout Peter Zijlstra
2013-09-30 15:22 ` [PATCH 6/6] sched, wait: Make the __wait_event*() interface more friendly Peter Zijlstra
2013-10-01  6:39   ` Ingo Molnar [this message]
2013-09-30 15:50 ` [PATCH 0/6] sched, wait: Collapse __wait_event macros -v4 Linus Torvalds
2013-09-30 16:11   ` Peter Zijlstra
2013-09-30 17:40 ` Oleg Nesterov
2013-09-30 18:00   ` Oleg Nesterov
2013-09-30 18:09   ` Peter Zijlstra
2013-09-30 18:13     ` Oleg Nesterov
2013-10-01 14:09       ` Oleg Nesterov
2013-10-01 14:39         ` Peter Zijlstra
2013-10-01 15:16           ` Oleg Nesterov
2013-10-01 17:01 ` [RFC] introduce prepare_to_wait_event() Oleg Nesterov
2013-10-01 17:25   ` Peter Zijlstra
2013-10-01 17:33     ` Oleg Nesterov
2013-10-01 17:44       ` Peter Zijlstra

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=20131001063954.GA19111@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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