From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] complete crash with ondemand scheduler
Date: Sun, 5 Aug 2007 16:29:43 +0200 [thread overview]
Message-ID: <d257c3560708050729u72a5b808t3e238905fa5f7c1a@mail.gmail.com> (raw)
In-Reply-To: <20070805090038.GD17442@ifa.hawaii.edu>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
i don't want to have to adjust it. i want it to step by default as i need,
and if there are daemons and better governors (the conservative one is
better in my opionion) i don't really understand why i should something that
will bother me with tunings when there are things that don't need them and
which perform better?!
2007/8/5, Joshua Hoblitt <jhoblitt@ifa.hawaii.edu>:
>
> On Sun, Aug 05, 2007 at 09:24:17AM +0200, Bernhard Auzinger wrote:
>
> > I think you are wrong, because the ondemand governor does also switch
> between
> > all available frequencies. For example my amd64X2 is capable of
> > 1000,1800,2000,2200,2400MHz and the ondemand governor does switch very
> well
> > between these frequencies if needed.
i repeat: on my 2 systems it didn't worked in that way, so i don't want to
spend time bothering about tunings when there is really no need for that.
That is correct, it moves one "step" per polling cycle the rate of which
> can be adjusted via the sysfs interface.
>
> -J
>
> --
>
>
[-- Attachment #2: Type: text/html, Size: 1466 bytes --]
next prev parent reply other threads:[~2007-08-05 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 11:43 [gentoo-amd64] complete crash with ondemand scheduler Raffaele BELARDI
2007-08-02 19:13 ` Beso
2007-08-02 23:32 ` Joshua Hoblitt
2007-08-03 9:28 ` Beso
2007-08-03 10:15 ` Raffaele BELARDI
2007-08-03 12:50 ` Beso
2007-08-04 23:11 ` Joshua Hoblitt
2007-08-05 14:25 ` Beso
2007-08-05 7:24 ` Bernhard Auzinger
2007-08-05 9:00 ` Joshua Hoblitt
2007-08-05 14:29 ` Beso [this message]
2007-08-06 4:25 ` Joshua Hoblitt
2007-08-03 6:01 ` [gentoo-amd64] " Raffaele BELARDI
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=d257c3560708050729u72a5b808t3e238905fa5f7c1a@mail.gmail.com \
--to=givemesugarr@gmail.com \
--cc=gentoo-amd64@lists.gentoo.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