Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-05 Thread Con Kolivas
On Wednesday 05 April 2006 09:45, Robert Reif wrote: > One problem that I am seeing is that there is no practical way to > guarantee synchronization between the sound card hardware and the > sound card thread. OSS doesn't support poll/select reliably in > all drivers and the esd driver just writes

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-05 Thread Con Kolivas
On Wednesday 05 April 2006 08:27, Willie Sippel wrote: > Am Dienstag, 4. April 2006 16:46 schrieb Andreas Mohr: > > Hi, > > > > On Wed, Apr 05, 2006 at 12:36:06AM +1000, Con Kolivas wrote: > > > On Wednesday 05 April 2006 00:34, Andreas Mohr wrote: > > > &g

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-05 Thread Con Kolivas
On Wednesday 05 April 2006 11:42, Segin wrote: > Although I have ALSA in my kernel, I also use the OSS compatability, and > on top of that, use more regulary than ALSA directly. I use OSS in Wine > cause the WineALSA driver is fustrating, and wants odd settings > (something about DirectSound emulat

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-05 Thread Con Kolivas
On Wednesday 05 April 2006 21:47, Aneurin Price wrote: > Con Kolivas wrote: > > Is it kernel dependant? Does 2.6.11 for example exhibit the problem or > > only recent kernels? Or has noone tried an older kernel like that? > Just to reiterate since everybody seems to forget this

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-04 Thread Con Kolivas
On Wednesday 05 April 2006 00:46, Andreas Mohr wrote: > Hi, > > On Wed, Apr 05, 2006 at 12:36:06AM +1000, Con Kolivas wrote: > > On Wednesday 05 April 2006 00:34, Andreas Mohr wrote: > > > And this all should work perfectly well with NON-soft-realtime > > > s

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-04 Thread Con Kolivas
On Wednesday 05 April 2006 00:06, Mike Hearn wrote: > > Is it kernel dependant? Does 2.6.11 for example exhibit the problem or > > only recent kernels? Or has noone tried an older kernel like that? > > I think this has been a problem since time immemorial. Previous > discussions like this one have

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-04 Thread Con Kolivas
On Wednesday 05 April 2006 00:34, Andreas Mohr wrote: > Hi, > > On Wed, Apr 05, 2006 at 12:10:37AM +1000, Con Kolivas wrote: > > On Wednesday 05 April 2006 00:06, Mike Hearn wrote: > > > I think for now I shall just maintain this patch out of tree so savvy > > >

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-04 Thread Con Kolivas
On Wednesday 05 April 2006 00:49, Mike Hearn wrote: > >>> Don't give up now as you will convince everyone else there is no > >>> solution and only your patch will make games work. Your attitude is > >>> defeatist because you're convinced that real time scheduling is your > >>> saviour. > > I don't

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-04 Thread Con Kolivas
On Tuesday 04 April 2006 23:29, Mike Hearn wrote: > > I know I didn't offer a solution, just standard rules for multithreaded > > application writing. The fact that wine is a compatibility layer rather > > than its own application is most of your problem. Is there no way wine > > could have an audi

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-04 Thread Con Kolivas
On Tuesday 04 April 2006 23:46, Mike Hearn wrote: > > By infinite loop I assume you mean it is sleeping, not burning cpu... But > > anyway, is this a separate thread or part of a monolithic "wine"? > > Right, it blocks on a message pipe. It's a separate thread. > > > I think fragile is too harsh a

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-04 Thread Con Kolivas
On Tuesday 04 April 2006 22:42, Mike Hearn wrote: > > What strikes me is that people are very happy to think that the kernel is > > going to fix this problem. I have to tell you there will be no more > > infrastructure put into the kernel anytime soon to help you here. > > I'm confused about this p

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

2006-04-04 Thread Con Kolivas
On Tue, 4 Apr 2006 01:47 am, Andreas Mohr wrote: > Hi, > > [sneaked in another CC, JFYI ;] Oh hi! This is the first time this thread has been brought to my attention. > On Mon, Apr 03, 2006 at 04:29:43PM +0100, Mike Hearn wrote: > > And even then, SCHED_ISO is a long way off and may never be merg

Re: Wine scheduling and threading issues [was Re: Threading issues...]

2005-01-16 Thread Con Kolivas
Jeremy White wrote: Hi all, This is simply a renaming and reorganizing post; Dimi wacked me with a clue bat, and I am now looping Ingo Molnar into this conversation (and I am doing it at great haste since he made noises about helping ). The thread started here: http://www.winehq.org/hypermail/win

Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

2005-01-14 Thread Con Kolivas
Ove Kaaven wrote: fre, 14,.01.2005 kl. 13.06 +1100, skrev Con Kolivas: Well the scheduler is not going to be rewritten any time soon (trust me, I've tried :P). Tell me what remaining requirements your threads have that you are unable to achieve at the moment and I'll see if I can hel

Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

2005-01-14 Thread Con Kolivas
Jeremy White wrote: Photoshop has a thread that runs that samples the mouse position every 5 ms; if it doesn't get it's samples in the right amount of time, you don't draw smooth curves. (It may be a timer event callback routine, or a thread that is woken up by a timer event, I can't recall exact

Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

2005-01-14 Thread Con Kolivas
Jeremy White wrote: Specifically, there are other areas of interest when you think about timing and scheduling. First is the Windows very clear cut 'foreground window' boost. I have no idea how this maps into the Linux interactivity strategy. They seem to be roughly equivalent, and I never found

Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

2005-01-13 Thread Con Kolivas
Jeremy White wrote: Fyi, I spent a great deal of time this past fall exploring Wine scheduling issues, and I thought I would post what I learned. The most critical point is Wine was pretty badly broken; it simply had a number of flaws in how scheduling was done. First, the winmm timer, used by a lo

Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

2004-09-03 Thread Con Kolivas
Michael Buesch writes: Quoting Andreas Mohr <[EMAIL PROTECTED]>: Hi, On Sun, Aug 29, 2004 at 10:07:18PM +1000, Con Kolivas wrote: > Audio runs as a separate thread outside of wine potentially through who > knows how many layers as a combination of both process and kernel > co

Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

2004-09-02 Thread Con Kolivas
Mike Hearn wrote: Other solution is just to detect this and ask the user to rerun Wine as root. I don't think that'd be a big deal. But then that brings up the issue of users not being able to run wine merely because they don't have root access, i.e. users on a Linux system in a business environm

Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

2004-09-02 Thread Con Kolivas
Robert Shearman wrote: Mike Hearn wrote: I wouldn't trust it. An app just misbehaving can trash important parts of your filesystem. Suid root is just a bad idea, windows being linux aware or not. Just for mild amusement I think someone being funky got a windows virus to work under wine if I reca

Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

2004-09-02 Thread Con Kolivas
Mike Hearn wrote: I wouldn't trust it. An app just misbehaving can trash important parts of your filesystem. Suid root is just a bad idea, windows being linux aware or not. Just for mild amusement I think someone being funky got a windows virus to work under wine if I recall correctly. Sure. Do

Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

2004-08-29 Thread Con Kolivas
Ove Kaaven wrote: søn, 29.08.2004 kl. 04.13 skrev Michael Chang: I argued with myself about the logic in this for ages. The best I could come up with is - I don't know :| I'd need to know about windows scheduling (which I don't) Obviously, if Win apps have been written to expect this, there's doc

Re: [ck] Re: Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

2004-08-28 Thread Con Kolivas
Mike Hearn wrote: Well, apparently we don't use sched_yield, so the problem must lie somewhere else. Maybe Con can help us out here? Alexandre says he doesn't know what the issue is either and somebody needs to investigate. I guess we do need to concern ourselves over the details :) Interesting