From: Paul Mundt <lethal@linux-sh.org>
To: Valdis.Kletnieks@vt.edu
Cc: mgross@linux.intel.com, Randy Dunlap <randy.dunlap@oracle.com>,
linux-pm <linux-pm@lists.linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] QoS params patch
Date: Thu, 27 Sep 2007 12:18:21 +0900 [thread overview]
Message-ID: <20070927031821.GA26307@linux-sh.org> (raw)
In-Reply-To: <22087.1190861583@turing-police.cc.vt.edu>
On Wed, Sep 26, 2007 at 10:53:03PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 26 Sep 2007 17:40:20 PDT, Mark Gross said:
> > --- linux-2.6.23-rc8/kernel/Makefile 2007-09-26 13:54:54.000000000 -0700
> > +++ linux-2.6.23-rc8-qos/kernel/Makefile 2007-09-26 14:06:38.000000000 -
> 0700
> > @@ -9,7 +9,7 @@
> > rcupdate.o extable.o params.o posix-timers.o \
> > kthread.o wait.o kfifo.o sys_ni.o posix-cpu-timers.o mutex.o \
> > hrtimer.o rwsem.o latency.o nsproxy.o srcu.o die_notifier.o \
> > - utsname.o
> > + utsname.o qos_params.o
>
> So I don't get a choice in the matter if I will be dragging this thing
> around in my kernel, even if I have no intention of using the functionality?
>
You don't get that option with latency.c either at the moment, and it's
arguable whether it's even worth it. The more curious thing is that while
this qos params seems to be an evolution of Arjan's latency.c (and the
drivers that are using it are updated in the rest of the patch set),
latency.c itself is still compiled in. Is this an oversight, or was it
intentional? One set of latency hinting APIs only, please :-)
next prev parent reply other threads:[~2007-09-27 3:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 22:37 [RFC] QoS power Management enabling patch set Mark Gross
2007-09-26 22:40 ` [RFC] QoS params patch Mark Gross
2007-09-26 23:41 ` Randy Dunlap
2007-09-27 0:40 ` Mark Gross
2007-09-27 2:53 ` Valdis.Kletnieks
2007-09-27 3:18 ` Paul Mundt [this message]
2007-09-27 15:17 ` Mark Gross
2007-09-27 15:36 ` Mark Gross
2007-09-27 13:00 ` roel
2007-09-27 2:24 ` Paul Mundt
2007-09-27 4:05 ` Randy Dunlap
2007-09-27 15:37 ` Mark Gross
2007-09-27 20:17 ` [RFC] QoS params patch update Mark Gross
2007-09-28 0:08 ` Paul Mundt
2007-09-27 16:21 ` [RFC] QoS params patch Mark Gross
2007-09-28 6:25 ` Andrew Morton
2007-09-28 6:41 ` Paul Mundt
2007-09-28 17:22 ` Mark Gross
2007-09-28 17:19 ` Mark Gross
2007-09-28 18:51 ` Andrew Morton
2007-10-01 16:11 ` Mark Gross
2007-09-26 22:42 ` [RFC] QoS power Management enabling patch set Mark Gross
2007-09-26 22:45 ` [RFC] QoS power example / hack Mark Gross
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=20070927031821.GA26307@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mgross@linux.intel.com \
--cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox