Re: CPU Frequency Scaling and Niceness

[Evan]

On Thu, Apr 30, 2009 at 9:49 PM, Jan Claeys  wrote:

> Op dinsdag 28-04-2009 om 22:09 uur [tijdzone +0300], schreef Marius
> Gedminas:
> > Why is it a bug?  According to Matthew Garrett, to save power, you
> > want to finish executing a task as soon as possible, which means
> > running for a shorter time at 100% speed.
>
> That won't save power for an application that runs forever though, which
> is what Evan wants (running a BOINC client).
>
> Seems like a good use-case to me; any (almost) perpetual background-task
> should not scale up the CPU frequency.  How to implement that behaviour
> is up to the linux devs though...  ;)
>

It is already implemented in the form of the ignore_nice_load setting. This
site [1] explains it well.

The bug report [2] is because in Jaunty, this setting is ignored, and not
honoured.

[1] http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
[2] https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/368809


Evan
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Raising issues (games etc)

[Matthew Paul Thomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Alex Cockell wrote on 01/05/09 18:09:
>...
> Sorry for being really dense, but would "filing a bug" be your term for
> what I would know as "raising an incident ticket"?
>...

Probably not. If you are looking for help fixing or working around a
problem with Ubuntu, for free or for pay, there are a several support
sources available. 

Reporting a bug is for directly helping developers to improve the
software. To report a bug you should be able to clearly describe how to
reproduce the problem, and you should be willing and able to answer
technical questions about the computer where the problem occurs
(including testing to see if it occurs with newer versions of the same
program).

Cheers
- --
Matthew Paul Thomas
http://mpt.net.nz/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkn7O0EACgkQ6PUxNfU6ecoKNQCeKwZ0wLVPX7hUxoKogMGHcIC4
RwIAoKVsSEADOKSsJLS/oevWSMpr8Ohr
=I5i2
-END PGP SIGNATURE-

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Notify OSD to be discussed at UDS Karmic

[Matthew Paul Thomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Since there were complaints about insufficient notice last time ... :-)

At UDS Karmic this month, there will be a session for discussing
improvements to the Notify OSD notification server.


Topics for discussion will include:
*   experimenting with better positioning for the notification bubbles
*   improving the appearance and behavior (making composited bubbles
more obviously unclickable, and non-composited bubbles classier)
*   implementing the duration rules, so that notifications with longer
text are shown for longer
*   better handling of long backlogs of notifications
*   investigating whether we can use non-critical priorities for
anything useful
*   helping to get the FreeDesktop.org notifications specification to
1.0
*   a Qt implementation
*   investigating a "do-not-disturb" mode
*   accessibility, e.g. sound theme compliance and maybe alt text for
icons
*   media key confirmation bubbles (Play, Pause, Previous, Next)
*   suppressing bubbles when any window is full-screen
*   a test suite for the rendering layer.

If you want to take part in the discussion, keep an eye on the schedule
 to find out when the session will
be. If you can't attend (either physically or virtually) but have
suggestions you'd like considered, please add them to the Notify OSD
comments page. 

Thanks
- --
Matthew Paul Thomas
http://mpt.net.nz/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkn7LukACgkQ6PUxNfU6ecqolQCfdFoth18NLURUbvFOC5QSuKkz
xoYAnio1ULJNnR2cgvk3zs7qhAMckfWs
=uIjt
-END PGP SIGNATURE-

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Raising issues (games etc)

[Alex Cockell]

Hi folks,

Sorry for being really dense, but would "filing a bug" be your term for
what I would know as "raising an incident ticket"?

Apologies again...


-- 

Alex Cockell
Reading, Berks, UK
alcock...@eclipse.co.uk


-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Ubuntu gaming team - raising incidents

[Andrew]

On Fri, May 1, 2009 at 11:15 AM, Mike Jones  wrote:
>
>> >Hi folks,
>> >
>> >> If users are assigning bugs to a team, in virtually all cases they are
>> >> wrong to do so.  Assignment indicates some expectation that work will
>> >> be
>> >> done.  End users do not have the right to direct developers (whether
>> paid
>> >> or volunteer).
>> >
>> >Speaking as an end-user, could the original poster be referring to
>> >initially raising an incident against the team "Linux"?  I believe this
>> >is where an end-user would log the initial incident report to?
>> >
>> >Sorry for the use of ITIL terms - please feel free to translate to
>> >Ubuntu nomenclature... I think ITIL after working in support for quite a
>> >long time..
>> >
>> >Surely an end-user isn't *directing* developers, but raising a request?
>> >
>> >Thoughts?
>>
>> For users that don't have some kind of commercial support contract (they
>> have their own, separate mechanisms for rasing issues), filing a bug is
>> the
>> appropriate method to bring a system deficiency to developers.  In Ubuntu,
>> bug assignment generally carries the connotation of work assigned (either
>> self assigned or by a supervisor in some cases).  Some teams may have
>> different policies, but in general it is not appropriate.
>>
>> Scott K
>>
> I'm not sure I understand why users have the ability to assign bugs if they
> should not be doing so. Ubuntu is used by a very broad audience. Some of
> this audience does not understand what a bug report is for, and might
> consider the bug filing apparatus to be similar to tech-support. It isn't
> necessarily that the users would assign a bug maliciously, but at the same
> time why do normal users have the ability if they should not be using it?
>
> -Mike

Well for one thing, many "normal users" also give back and fix bugs
themselves despite not being part of any official development team. As
part of this they assign themselves. There are other potential use
cases as well. I've seen devs on IRC talking about a bug with a user,
and _ask_ them to assign them in order to put it on their to-do list.
Assigning your self also used to be part of the bug triage workflow.
While that has wisely changed for Ubuntu, some upstreams using LP
might still do this.

In general, Launchpad seems to be very open about most permissions.
While this does sometimes become an issue, I personally think that it
also encourages people to get involved.

Only once has someone seen my name in a changelog (strangely enough,
not the most recent upload) and assigned me to a bug. I think this is
more of an issue with teams (ie someone assigning MOTU).

- Andrew Starr-Bochicchio

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss

Re: Ubuntu gaming team - raising incidents

[Mike Jones]

> >Hi folks,
> >
> >> If users are assigning bugs to a team, in virtually all cases they are
> >> wrong to do so.  Assignment indicates some expectation that work will be
> >> done.  End users do not have the right to direct developers (whether
> paid
> >> or volunteer).
> >
> >Speaking as an end-user, could the original poster be referring to
> >initially raising an incident against the team "Linux"?  I believe this
> >is where an end-user would log the initial incident report to?
> >
> >Sorry for the use of ITIL terms - please feel free to translate to
> >Ubuntu nomenclature... I think ITIL after working in support for quite a
> >long time..
> >
> >Surely an end-user isn't *directing* developers, but raising a request?
> >
> >Thoughts?
>
> For users that don't have some kind of commercial support contract (they
> have their own, separate mechanisms for rasing issues), filing a bug is the
> appropriate method to bring a system deficiency to developers.  In Ubuntu,
> bug assignment generally carries the connotation of work assigned (either
> self assigned or by a supervisor in some cases).  Some teams may have
> different policies, but in general it is not appropriate.
>
> Scott K
>
> I'm not sure I understand why users have the ability to assign bugs if they
should not be doing so. Ubuntu is used by a very broad audience. Some of
this audience does not understand what a bug report is for, and might
consider the bug filing apparatus to be similar to tech-support. It isn't
necessarily that the users would assign a bug maliciously, but at the same
time why do normal users have the ability if they should not be using it?

-Mike
-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss