From: Len Brown <len.brown@intel.com>
To: Adam Belay <ambx1@neo.rr.com>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com, rml@ximian.com,
mochel@digitalimplant.org
Subject: Re: [RFC] Bus Resource Management
Date: 23 Aug 2004 15:39:22 -0400 [thread overview]
Message-ID: <1093289962.17215.45.camel@dhcppc4> (raw)
In-Reply-To: <20040819133550.GH3824@neo.rr.com>
On Thu, 2004-08-19 at 09:35, Adam Belay wrote:
> 2.) Sysfs user interface
> - userspace applications can determine resource usage and
> dependencies.
> - userspace applications can disable and enable devices
> - userspace applications can assign resources to a device
> - userspace applications can pause the operation of a device, and
> rebalance
> its resources
I agree that run-time hotplug policy and re-balancing would all be very
snappy from user-space - users should be in charge when setting policy.
Heck, humans may even be needed to make some decisions regarding
resource conflicts...
But I'm wondering where the proper line is between that and the resource
management that we have to do on boot before user-space exists.
cheers,
-Len
next prev parent reply other threads:[~2004-08-24 0:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 13:35 [RFC] Bus Resource Management Adam Belay
2004-08-23 19:39 ` Len Brown [this message]
2004-08-23 20:00 ` Adam Belay
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=1093289962.17215.45.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=ambx1@neo.rr.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=rml@ximian.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