From: Peter Zijlstra <peterz@infradead.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Tejun Heo <tj@kernel.org>,
Peter Boonstoppel <pboonstoppel@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
Andy Walls <awalls@md.metrocast.net>,
Diwakar Tundlam <dtundlam@nvidia.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 1/1] kthread: disable preemption during complete()
Date: Thu, 26 Jul 2012 21:29:52 +0200 [thread overview]
Message-ID: <1343330992.26034.92.camel@twins> (raw)
In-Reply-To: <20120726155409.GB20964@redhat.com>
On Thu, 2012-07-26 at 17:54 +0200, Oleg Nesterov wrote:
> Yes, but this "avoid the preemption after wakeup" can actually help
> kthread_bind()->wait_task_inactive() ?
Yeah.
> This reminds me, Peter had a patch which teaches wait_task_inactive()
> to use sched_in/sched_out notifiers to avoid the polling...
I did, but from what I could remember you shot holes in it and I didn't
find a way to plug them and not make it a bigger mess than it is now :/
next prev parent reply other threads:[~2012-07-26 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 0:05 [PATCH 1/1] kthread: disable preemption during complete() Peter Boonstoppel
2012-07-25 0:09 ` Tejun Heo
2012-07-25 22:35 ` Peter Boonstoppel
2012-07-25 22:40 ` Tejun Heo
2012-07-26 8:04 ` Peter Zijlstra
2012-07-26 10:47 ` Thomas Gleixner
2012-07-26 15:54 ` Oleg Nesterov
2012-07-26 19:29 ` Peter Zijlstra [this message]
2012-07-26 21:16 ` Peter Boonstoppel
2012-08-01 7:14 ` Thomas Gleixner
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=1343330992.26034.92.camel@twins \
--to=peterz@infradead.org \
--cc=awalls@md.metrocast.net \
--cc=dtundlam@nvidia.com \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=pboonstoppel@nvidia.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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