All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	mingo@elte.hu, rnalumasu@gmail.com
Subject: Re: + do_wait-wakeup-optimization.patch added to -mm tree
Date: Thu, 4 Dec 2008 16:26:01 +0100	[thread overview]
Message-ID: <20081204152601.GB8816@redhat.com> (raw)
In-Reply-To: <20081204005203.C795EFC3AB@magilla.sf.frob.com>

On 11/23, Roland McGrath wrote:
>
> > > +static int do_wait_wake_function(wait_queue_t *curr, unsigned mode, int sync,
> > > +				 void *key)
> > > +{
> > > +	struct task_struct *task = current;
> >
> > I think we can fix (and simplify) this code if we change __wake_up_parent(),
> > it should call __wake_up(key => p), so we can do
> >
> > 	struct task_struct *task = key;
>
> I don't see an exposed __wake_up* variant that both passes a "key" pointer
> through and does "sync".  For __wake_up_parent, "sync" is quite desireable.

Well, yes... and __wake_up_common() is static. Perhaps we can make a new
helper. I must admit, I don't understand what "sync" actually means nowadays.

> > > +	if (!needs_wakeup(task, w))
> > > +		return 0;
> > > +
> > > +	return default_wake_function(curr, mode, sync, key);
> >
> > perhaps autoremove_wake_function() makes more sense.
>
> Why?  The do_wait loop will have to go through again and still might just
> sleep again.  The explicit remove at the end of do_wait seems fine to me.

Yes, yes, I was wrong. I forgot about "repeat:" in do_wait().

Oleg.


  reply	other threads:[~2008-12-04 15:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 20:15 + do_wait-wakeup-optimization.patch added to -mm tree akpm
2008-11-23 21:39 ` Oleg Nesterov
2008-11-23 21:55   ` do_wait() vs do_notify_parent_cldstop() theoretical race? Oleg Nesterov
2008-11-24  7:31     ` Roland McGrath
2008-12-04  1:05     ` Roland McGrath
2008-11-24  7:26   ` + do_wait-wakeup-optimization.patch added to -mm tree Roland McGrath
2008-12-04 15:26     ` Oleg Nesterov [this message]
2008-12-04 20:59       ` Roland McGrath
2008-12-04  1:06   ` Roland McGrath

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=20081204152601.GB8816@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rnalumasu@gmail.com \
    --cc=roland@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.