public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jordan Crouse" <jordan.crouse@amd.com>
To: linux-pm@lists.osdl.org
Subject: Re: Power Management Policies
Date: Wed, 27 Apr 2005 08:57:17 -0600	[thread overview]
Message-ID: <20050427145717.GA20602@cosmic.amd.com> (raw)
In-Reply-To: <200504270722.31321.david-b@pacbell.net>

[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]

On 27/04/05 07:22 -0700, David Brownell wrote:
> I don't see major vendors wanting to move away from "closed" models
> at the lower end, or in fact whereever they have the power to dictate
> customer "preferences".  (The latter case is also known as a "market
> failure", except by radical corporatists...)  But for higher end products,
> or when customers truly have (or need!!) choices, then "open" is more
> usually the answer.

Indeed.  Really, my point was that massive userland based configuration is
better suited to systems with known configurations and vendors motivated to
spend the time and expense to tune the system.

As the system configuration opens up, it becomes less likely that the end user
will be willing to go to the same effort.  When you hit the desktop/laptop 
market, only the very uber of geeks will even consider it.

Which is why I think that userland tuning should be an option, and not
mandatory.  A wide majority of the users across the Linux spectrum might 
not care what the wake up latency of their NIC is, but I think that there are
enough that do to make a userland configuration framework useful.

-- 
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>


[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2005-04-27 14:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-17 21:15 [RFC] Power Management Policies Adam Belay
2005-04-18 15:39 ` Jordan Crouse
2005-04-22 20:05   ` Pavel Machek
2005-04-27 14:08     ` David Brownell
2005-04-27 14:48       ` Pavel Machek
2005-04-28  0:05         ` David Brownell
2005-04-28  8:23           ` Pavel Machek
2005-04-28 17:16             ` David Brownell
2005-04-28 18:59               ` Pavel Machek
2005-04-28 20:28                 ` David Brownell
2005-04-23  7:18   ` Adam Belay
2005-04-27 14:01     ` David Brownell
2005-04-27 14:22   ` David Brownell
2005-04-27 14:57     ` Jordan Crouse [this message]
2005-04-27 16:03       ` David Brownell

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=20050427145717.GA20602@cosmic.amd.com \
    --to=jordan.crouse@amd.com \
    --cc=linux-pm@lists.osdl.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