From: David Miller <davem@davemloft.net>
To: viresh.kumar@linaro.org
Cc: tj@kernel.org, linaro-kernel@lists.linaro.org,
patches@linaro.org, robin.randhawa@arm.com,
Steve.Bannister@arm.com, Liviu.Dudau@arm.com,
charles.garcia-tobin@arm.com, arvind.chauhan@arm.com,
airlied@redhat.com, axboe@kernel.dk, tglx@linutronix.de,
peterz@infradead.org, mingo@redhat.com, rostedt@goodmis.org,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH V4 2/4] PHYLIB: queue work on unbound wq
Date: Sun, 31 Mar 2013 12:45:22 -0400 (EDT) [thread overview]
Message-ID: <20130331.124522.495583446567617837.davem@davemloft.net> (raw)
In-Reply-To: <6be4e9ad2048a2a9d60143f58931c3fe94770175.1364740180.git.viresh.kumar@linaro.org>
From: Viresh Kumar <viresh.kumar@linaro.org>
Date: Sun, 31 Mar 2013 20:01:45 +0530
> Phylib uses workqueues for multiple purposes. There is no real dependency of
> scheduling these on the cpu which scheduled them.
>
> On a idle system, it is observed that and idle cpu wakes up many times just to
> service this work. It would be better if we can schedule it on a cpu which the
> scheduler believes to be the most appropriate one.
>
> This patch replaces system_wq with system_unbound_wq for PHYLIB.
>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: netdev@vger.kernel.org
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2013-03-31 16:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 14:31 [PATCH V4 0/4] Queue work on UNBOUND wq Viresh Kumar
2013-03-31 14:31 ` [PATCH V4 1/4] workqueue: Add system wide system_freezable_unbound_wq Viresh Kumar
2013-04-01 5:20 ` Amit Kucheria
2013-04-01 5:25 ` Viresh Kumar
2013-04-08 16:59 ` Steven Rostedt
2013-04-09 4:11 ` Viresh Kumar
2013-03-31 14:31 ` [PATCH V4 2/4] PHYLIB: queue work on unbound wq Viresh Kumar
2013-03-31 16:45 ` David Miller [this message]
2013-03-31 14:31 ` [PATCH V4 3/4] block: " Viresh Kumar
2013-03-31 18:19 ` Tejun Heo
2013-04-01 6:31 ` Viresh Kumar
2013-04-03 21:54 ` Tejun Heo
2013-04-05 9:47 ` Viresh Kumar
2013-04-05 12:22 ` Tejun Heo
2013-04-08 10:24 ` Viresh Kumar
2013-04-08 10:37 ` Amit Kucheria
2013-04-08 11:02 ` Viresh Kumar
2013-04-08 11:13 ` Jens Axboe
2013-04-08 11:14 ` Viresh Kumar
2013-04-09 7:30 ` Viresh Kumar
2013-04-09 9:18 ` Amit Kucheria
2013-04-09 9:35 ` Viresh Kumar
2013-04-09 9:53 ` Amit Kucheria
2013-04-09 9:55 ` Viresh Kumar
2013-04-09 9:58 ` Amit Kucheria
2013-04-09 10:11 ` Viresh Kumar
2013-04-09 18:30 ` Tejun Heo
2013-04-22 6:20 ` Viresh Kumar
2013-04-23 20:24 ` Tejun Heo
2013-03-31 14:31 ` [PATCH V4 4/4] fbcon: " 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=20130331.124522.495583446567617837.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=airlied@redhat.com \
--cc=arvind.chauhan@arm.com \
--cc=axboe@kernel.dk \
--cc=charles.garcia-tobin@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=patches@linaro.org \
--cc=peterz@infradead.org \
--cc=robin.randhawa@arm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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).