Re: [pulseaudio-discuss] rtkit: add pid as argument

2010-05-08 Thread Maarten Lankhorst
Hello, 2010/5/7 David Henningsson launchpad@epost.diwic.se: On 2010-04-25 22:11, Lennart Poettering wrote: On Sun, 25.04.10 21:41, David Henningsson (launchpad@epost.diwic.se) wrote: which handle corresponds to the thread, or even if that handle is local or not. Wineserver

Re: [pulseaudio-discuss] rtkit: add pid as argument

2010-05-08 Thread Lennart Poettering
On Sat, 08.05.10 11:21, Maarten Lankhorst (m.b.lankho...@gmail.com) wrote: So let my rephrase my question to Maarten: Since there is no equivalent to RLIMIT_RTTIME in Windows, applications might assume they can run in RT for extended periods of time. This might be considered bad

Re: [pulseaudio-discuss] rtkit: add pid as argument

2010-05-07 Thread Lennart Poettering
On Wed, 05.05.10 01:10, Maarten Lankhorst (m.b.lankho...@gmail.com) wrote: Patch looks goot to me. But could you fix one thing: I think MakeThreadRealtimeWithPID() (or something like tht) would be a better name than MakeThreadRealtime2(). After examples like wait(), wait3() and wait4() in

Re: [pulseaudio-discuss] rtkit: add pid as argument

2010-05-06 Thread David Henningsson
On 2010-04-25 22:11, Lennart Poettering wrote: On Sun, 25.04.10 21:41, David Henningsson (launchpad@epost.diwic.se) wrote: which handle corresponds to the thread, or even if that handle is local or not. Wineserver controls this information so all requests that involve handles involve

Re: [pulseaudio-discuss] rtkit: add pid as argument

2010-05-04 Thread Maarten Lankhorst
Hello, On 25-04-10 02:52, Lennart Poettering wrote: ...snip OK, I am convinced. ;-) And yes, your use of rktit certainly makes a lot of sense. Patch looks goot to me. But could you fix one thing: I think MakeThreadRealtimeWithPID() (or something like tht) would be a better name than

Re: [pulseaudio-discuss] rtkit: add pid as argument

2010-04-25 Thread David Henningsson
Maarten Lankhorst wrote: Well, the use case would be wine's wineserver. On windows programs usually set audio threads to THREAD_PRIORITY_TIME_CRITICAL to indicate that they have to have a certain priority. But in windows thread handles are global, so doing it inside wine's 'ntdll' library

Re: [pulseaudio-discuss] rtkit: add pid as argument

2010-04-25 Thread Lennart Poettering
On Sun, 25.04.10 21:41, David Henningsson (launchpad@epost.diwic.se) wrote: which handle corresponds to the thread, or even if that handle is local or not. Wineserver controls this information so all requests that involve handles involve a wineserver call, in general. So racing cannot

[pulseaudio-discuss] rtkit: add pid as argument

2010-04-24 Thread Maarten Lankhorst
I'm not sure if I have the right mailing list, since there doesn't appear to be a a mailing list for rtkit. This is a patch that would allow you to set the realtime priority for another process then the one calling rtkit over dbus. This can be useful for a 'setsched' like utility, or for

Re: [pulseaudio-discuss] rtkit: add pid as argument

2010-04-24 Thread Maarten Lankhorst
Hello Lennart, On 25-04-10 01:42, Lennart Poettering wrote: On Sat, 24.04.10 01:18, Maarten Lankhorst (m.b.lankho...@gmail.com) wrote: I'm not sure if I have the right mailing list, since there doesn't appear to be a a mailing list for rtkit. This is a patch that would allow you to set

Re: [pulseaudio-discuss] rtkit: add pid as argument

2010-04-24 Thread Lennart Poettering
On Sun, 25.04.10 02:30, Maarten Lankhorst (m.b.lankho...@gmail.com) wrote: What concerns me a bit here is that RT programs must be written in an RT specific style to make sense. That means they must internally know which threads to make RT and which ones not, and when. From the outside of the