From: mark gross <markgross@thegnar.org>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: Kevin Hilman <khilman@ti.com>,
"Agarwal, Ramesh" <ramesh.agarwal@intel.com>,
markgross@thegnar.org, paulmck@vnet.ibm.com,
Praveen Chidambaram <pchidamb@gmail.com>,
Amit Kucheria <amit.kucheria@linaro.org>,
John Stultz <john.stultz@linaro.org>,
linux-pm@lists.linux-foundation.org,
Antti P Miettinen <amiettinen@nvidia.com>,
jeen.pihet@g62.linuxfoundation.org
Subject: Re: Plumbers: PM constraints micro-conf RFP
Date: Fri, 11 May 2012 07:10:33 -0700 [thread overview]
Message-ID: <20120511141033.GA2618@G62> (raw)
In-Reply-To: <CAORVsuUna_6oUYRf4_wfWcyR-n8CBMNWsdz5MaECLEdKFYs9SA@mail.gmail.com>
On Fri, May 11, 2012 at 09:02:02AM +0200, Jean Pihet wrote:
> Hi Mark,
>
> On Wed, May 2, 2012 at 4:36 PM, mark gross <markgross@thegnar.org> wrote:
> > This is a Request For Participation in a micro-conference at this years
> > Linux plumbers event. For this micro conference to happen we need to
> > reach a certain critical mass WRT participants as measured by submitted
> > talks associated to Power Management Constraints.
> That looks great! I hope some progress can be made in the area of the
> constraints frameworks design.
>
> > The To: list is populated with folks that I've had interactions with
> > over extending pm-qos or constraint based PM over the past year.
> >
> > If you are working on problems related to constraining the power /
> > performance of devices I am inviting your participation and request you
> > submit a proposal for presenting your problem space (preferred) and or
> > solution to a group of developers looking for a good solution to push
> > upstream. The talks will be about 20 min long as I want to get into
> > some design and implementation discussions after the requirements
> > definition is mostly finished.
> I can have something about the per-device PM QoS, starting from the
> ELC presentation [1], the current status and the next steps.
>
> [1] https://events.linuxfoundation.org/events/embedded-linux-conference/pihet
> The slides can be found at
> https://events.linuxfoundation.org/images/stories/pdf/lf_elc12_pihet.pdf.
>
> I am looking at the travel arrangements and will confirm asap.
>
> > I am interested in gathering user mode interface needs as well as kernel
> > mode.
> An agreement is needed on the APIs, especially for the user space.
>
> >
> > From a high level pm-constraints is a generalization of pm-qos to include
> > limiting performance as well as its current limiting of device
> > throttling.
> >
> > As performance limiting is typically used for any of the following:
> > 1) staying within thermal operational envelopes
> > 2) avoiding peak current
> > 3) extending battery life in active use cases
> >
> > I invite anyone working in any of these areas or pm-qos applications to
> > participate in this micro-conference.
> >
> > I will organize the micro-conference into 2 parts:
> > 1) problem statements with specific participant examples where
> > constraining the performance or throttling is needed.
> >
> > 2) high level design brain storming.
> >
> > If the micro-conference happens (i.e. critical mass is reached) any
> > interested linux-plumbers attendees is very welcome to participate.
> >
> > Please send me an off list email if you want me to add you to my mutt
> > alias of interested parties I'll use to cc people on emails. Note: must
> > of the correspondence will cc linux-pm too.
> >
> > Please submit a proposal if you are interested in participating in this
> > with me. I know a number of people are working in this space for the
> > past few years now. I think its a good time to compare notes and at
> > least consolidate requirements and use cases. Perhaps we'll even come up
> > with a good design to implement in the process.
> >
> > thanks,
> > --mark
>
> Thanks for organizing!
>
I think it will be a good discussion and hopefully we'll make progress
all around on this topic.
BTW I'm sorry for mutilating your name and email in my original
posting.
--mark
next prev parent reply other threads:[~2012-05-11 14:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 14:36 Plumbers: PM constraints micro-conf RFP mark gross
2012-05-04 14:16 ` mark gross
2012-05-14 8:43 ` Antti P Miettinen
2012-05-14 13:35 ` mark gross
2012-05-09 18:35 ` Kevin Hilman
2012-05-09 18:54 ` Kevin Hilman
2012-05-11 7:02 ` Jean Pihet
2012-05-11 14:10 ` mark gross [this message]
2012-05-11 7:17 ` Valentin, Eduardo
2012-05-11 14:14 ` mark gross
[not found] ` <CAORVsuU3YDGq713jtmPCpJT=3eXqrvx_qU=uPK86XvDdzHSGtg@mail.gmail.com>
[not found] ` <4FB13CD3.8000505@ti.com>
[not found] ` <CAGF5oy-xduO-BjM1NcNvJG1LV1d-1h78v6mdpq5noRFMsxmjkg@mail.gmail.com>
[not found] ` <CAGF5oy9kKPW5BF9FPXXm8-=9O5AM+NhKxjOysJbDiwDF=RvpKw@mail.gmail.com>
2012-05-15 9:40 ` Jean Pihet
2012-05-15 11:00 ` Valentin, Eduardo
2012-05-15 12:58 ` Amit Kucheria
2012-05-16 0:13 ` mark gross
2012-05-17 11:17 ` Sundar
2012-05-17 11:30 ` Sundar
2012-05-16 0:09 ` mark gross
2012-05-16 9:45 ` Mansoor, Illyas
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=20120511141033.GA2618@G62 \
--to=markgross@thegnar.org \
--cc=amiettinen@nvidia.com \
--cc=amit.kucheria@linaro.org \
--cc=jean.pihet@newoldbits.com \
--cc=jeen.pihet@g62.linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=khilman@ti.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=paulmck@vnet.ibm.com \
--cc=pchidamb@gmail.com \
--cc=ramesh.agarwal@intel.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;
as well as URLs for NNTP newsgroup(s).