From: Tejun Heo <tj@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-kernel@vger.kernel.org, pjt@google.com,
paul.mckenney@linaro.org, tglx@linutronix.de,
suresh.b.siddha@intel.com, venki@google.com, mingo@redhat.com,
peterz@infradead.org, robin.randhawa@arm.com,
Steve.Bannister@arm.com, Arvind.Chauhan@arm.com,
amit.kucheria@linaro.org, vincent.guittot@linaro.org,
linaro-dev@lists.linaro.org, patches@linaro.org
Subject: Re: [PATCH V2 3/3] workqueue: Schedule work on non-idle cpu instead of current one
Date: Sun, 30 Sep 2012 17:54:55 +0900 [thread overview]
Message-ID: <20120930085455.GJ10383@mtj.dyndns.org> (raw)
In-Reply-To: <7d5c2cac08134446583624cc124d46d9726bdb2d.1348736069.git.viresh.kumar@linaro.org>
Hello, Viresh.
On Thu, Sep 27, 2012 at 02:34:05PM +0530, Viresh Kumar wrote:
> - A cpu has programmed a timer and is IDLE now.
> - CPU gets into interrupt handler due to timer and queues a work. As the CPU is
> currently IDLE, we can queue this work to some other CPU.
I'm still a bit confused, if the CPU is already running the IRQ
handler, the CPU is not idle by definition. What am I missing here?
Thanks.
--
tejun
next prev parent reply other threads:[~2012-09-30 8:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 9:04 [PATCH V2 0/3] Create sched_select_cpu() and use it in workqueues Viresh Kumar
2012-09-27 9:04 ` [PATCH V2 1/3] sched: Create sched_select_cpu() to give preferred CPU for power saving Viresh Kumar
2012-09-27 9:04 ` [PATCH V2 2/3] timer: hrtimer: Don't check idle_cpu() before calling get_nohz_timer_target() Viresh Kumar
2012-09-27 10:31 ` Viresh Kumar
2012-09-27 9:04 ` [PATCH V2 3/3] workqueue: Schedule work on non-idle cpu instead of current one Viresh Kumar
2012-09-28 6:03 ` Viresh Kumar
2012-09-30 8:54 ` Tejun Heo [this message]
2012-09-30 12:16 ` Viresh Kumar
2012-10-01 0:32 ` Tejun Heo
2012-10-01 3:47 ` Viresh Kumar
2012-10-01 9:12 ` Vincent Guittot
2012-10-15 4:38 ` [PATCH V2 0/3] Create sched_select_cpu() and use it in workqueues Viresh Kumar
2012-10-31 9:00 ` Viresh Kumar
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=20120930085455.GJ10383@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=Arvind.Chauhan@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=amit.kucheria@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=patches@linaro.org \
--cc=paul.mckenney@linaro.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=robin.randhawa@arm.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venki@google.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).