From: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
To: Dominik Brodowski
<linux-X3ehHDuj6sIIGcDfoQAp7OTW4wlIGRCZ@public.gmane.org>
Cc: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
ACPI-ML <linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Pallipadi Venkatesh
<venkatesh.pallipadi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [RFC 2/2] new C-state policy
Date: Wed, 11 Jan 2006 12:22:05 +0100 [thread overview]
Message-ID: <43C4EA5D.9040907@suse.de> (raw)
In-Reply-To: <20060111080402.GB599-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
Dominik Brodowski wrote:
> Hi,
>
>>> Also, the actual checking for bm_activity should be common code, e.g.
>> It's policy specific. Each policy could have its own method to calculate
>> bm_activity.
>
> What to do once bm_activity is or was detected, yes. How to determine
> whether there is current bus mastering activity, no -- that's core stuff,
> not policy stuff.
>
I had the experience that tweaking how bm_activity is detected could help a lot.
An aggressive policy might also accept some faulty transitions in respect of more
power saving achievements.
What about the way in the middle?:
A general check_bm_activity() function. This one can be overridden by more
complex policy drivers/modules.
I hope to get some time the next days to play with all this...
Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-01-11 11:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 4:12 [RFC 2/2] new C-state policy Shaohua Li
[not found] ` <1136866376.5750.29.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2006-01-10 23:17 ` Dominik Brodowski
[not found] ` <20060110231711.GB30356-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
2006-01-11 2:00 ` Shaohua Li
[not found] ` <1136944855.5750.61.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2006-01-11 8:04 ` Dominik Brodowski
[not found] ` <20060111080402.GB599-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
2006-01-11 11:22 ` Thomas Renninger [this message]
[not found] ` <43C4EA5D.9040907-l3A5Bk7waGM@public.gmane.org>
2006-01-11 13:51 ` Dominik Brodowski
[not found] ` <20060111135113.GA11960-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
2006-01-11 14:19 ` Thomas Renninger
2006-01-12 2:54 ` Shaohua Li
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=43C4EA5D.9040907@suse.de \
--to=trenn-l3a5bk7wagm@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-X3ehHDuj6sIIGcDfoQAp7OTW4wlIGRCZ@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=venkatesh.pallipadi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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