From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>, Ratan Nalumasu <rnalumasu@gmail.com>,
Roland McGrath <roland@redhat.com>,
Vitaly Mayatskikh <vmayatsk@redhat.com>,
linux-kernel@vger.kernel.org
Subject: [RFC,PATCH 0/2] do_wait() wakeup optimization
Date: Mon, 22 Jun 2009 19:04:32 +0200 [thread overview]
Message-ID: <20090622170432.GA4895@redhat.com> (raw)
Now that we have struct wait_opts, it is easy to solve the problems with
unnecessary wakeups from __wake_up_parent(). See the previous discussion
"+ do_wait-wakeup-optimization.patch added to -mm tree"
http://marc.info/?t=122729873300001
However, this complicates the code a bit and adds bytes 112 to compiled
code.
Ratan, Roland, do you think this optimisation is worthwhile?
Oleg.
next reply other threads:[~2009-06-22 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 17:04 Oleg Nesterov [this message]
[not found] ` <93ad5f3f0906230955x357ff9evc334d4a5c6def20@mail.gmail.com>
2009-06-23 14:30 ` [RFC,PATCH 0/2] do_wait() wakeup optimization Oleg Nesterov
[not found] ` <93ad5f3f0906240953v3b328f9bxca51cd9d3838d05c@mail.gmail.com>
2009-06-24 15:41 ` Oleg Nesterov
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=20090622170432.GA4895@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 \
--cc=vmayatsk@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.