From: mark gross <mgross@linux.intel.com>
To: linux-pm <linux-pm@lists.linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
aili@codeaurora.org, e1000-devel@lists.sourceforge.net,
bruce.w.allan@intel.com, linux-wireless@vger.kernel.org,
alsa-devel@alsa-project.org, tiwai@suse.de
Subject: [PATCH]PM_QOS-to-use-handle-based-requests 0/5
Date: Mon, 7 Dec 2009 09:05:17 -0800 [thread overview]
Message-ID: <20091207170517.GA5463@linux.intel.com> (raw)
This is a 5 patch series against linux-next-20091204 that changes pm_qos
to use a handle based access model for the kernel api. The string
based model was shown to be slow if pm_qos parameters are updated on hot
code paths.
Most of the design changes where motivated by a patch
aili@codeaurora.org sent me, and I spent some time cleaning up the API.
Also, I couldn't resist myself in renaming the API's a bit given the fact
that the signatures changed enough that I had to touch all the pm_qos
users anyway. I changed *requirement* to *request* in keeping with the
way PM_QOS really only does best effort. I've felt "requirement" is too
strong a word for the way it works.
If folks would rather me do the function re-naming in a separate patch
set we can do that too.
diffstat for the series against linux-next-20091204 :
drivers/acpi/processor_idle.c | 2
drivers/cpuidle/governors/ladder.c | 2
drivers/cpuidle/governors/menu.c | 2
drivers/net/e1000e/netdev.c | 22 ++-
drivers/net/igbvf/netdev.c | 6 -
drivers/net/wireless/ipw2x00/ipw2100.c | 11 +
include/linux/netdevice.h | 4
include/linux/pm_qos_params.h | 14 +-
include/sound/pcm.h | 3
kernel/pm_qos_params.c | 188 ++++++++++++++-------------------
net/mac80211/mlme.c | 2
sound/core/pcm.c | 3
sound/core/pcm_native.c | 14 +-
13 files changed, 132 insertions(+), 141 deletions(-)
--mgross
reply other threads:[~2009-12-07 17:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091207170517.GA5463@linux.intel.com \
--to=mgross@linux.intel.com \
--cc=aili@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tiwai@suse.de \
/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).