public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mgross@linux.intel.com
Cc: arjan@infradead.org, linux-pm@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	mark.gross@intel.com
Subject: Re: [PATCH] PM_QOS 1 of 2
Date: Thu, 4 Oct 2007 12:53:56 -0700	[thread overview]
Message-ID: <20071004125356.69e01dfe.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071001234528.GA5238@linux.intel.com>

On Mon, 1 Oct 2007 16:45:28 -0700
Mark Gross <mgross@linux.intel.com> wrote:

> The following is the cleaned up patch implementing the power management
> quality of service infrastructure discussed at the pm summit last June.
> 
> It is a genralization of the latency code put into the kernel last year
> by Arjan.
> 
> I would like to get this code included in the MM tree and to get some
> milage on it.
> 
> One thing to note about this implementation is that it exposes an
> interface to user space for registering pm_qos constraints in addition
> to the kernel exports.  Its a file based interface where a module can
> register a constraint and the constraint is valid only as long as the
> device node is held open.  Upon closing of the device node that
> constraint is cleaned up.
> 
> The patch set is in two postings.  
> 1) the base parameter code (this email)
> 2) replacing of latency.c/latenc.h with pm_qos_params.c/pm_qos_params.h

I wouldn't really view this as an adequate changelog.

- The Subject:s are pretty pathetic (please see my suggesed replacements)

- There is no description of the proposed new kernel<->userspace
  interfaces.

  As you are proposing new and permanent enhancements to the Linux API,
  this is something which should be spelled out in some detail.  Because we
  can change the implementation, but we can not ever change your interface.

  It would be nice to get that interface described in Documentation/
  somewhere, but it is *critical* that the design be fully revealed right
  now, during review.


Anyway, I am not a suitable person to review this submission.

I'll put the patches in -mm for a bit of eyeball-and-test (not that anyone
will know how to test it, due to the secret interfaces) but I do not want
to move this code into mainline until someone who is familiar with the PM
code has performed a detailed review of both the implementation and the
design (whatever that is!).

Please send new, complete descriptions of these patches.  I don't think
they can be effectively reviewed without that information.  Except perhaps
by someone who was at the PM summit, but that's cheating.


Thanks.

  parent reply	other threads:[~2007-10-04 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01 23:45 [PATCH] PM_QOS 1 of 2 Mark Gross
2007-10-03 17:59 ` [linux-pm] [PATCH] PM_QOS 2 " Mark Gross
2007-10-04 19:53 ` Andrew Morton [this message]
2007-10-04 20:39   ` [PATCH] PM_QOS 1 " 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=20071004125356.69e01dfe.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mark.gross@intel.com \
    --cc=mgross@linux.intel.com \
    --cc=torvalds@linux-foundation.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