[lkml]   [2000]   [Sep]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] Wine speedup through kernel module

Waldek Hebisch <> wrote:
> Well, I was thinking in the following way: we keep wineserver almost as
> now, only put some mutexes (semaphores) inside. We duplicate parts
> of wineserver code in the clients. We divide wineserver requests into
> two sets fast (easy) ones and slow. We modify send function in the
> client so that if request is fast one, than client enters a critical
> section (blocking wineserver!) and modifyes shared memory as needed.

You still have to do all the object maintainance yourself, plus you have no
clean-up-on-death code for certain circumstances (eg: SIGKILL).

How do you propose WaitFor*() should be implemented? Wait queues are hard to
do efficiently in userspace...

> Slow request should go usual way. The list of fast request should
> but most request should be slow.

Why? I personally want all requests to be as fast as possible, if only to
trounce Windows at its own game:->

> Simple minded implementation may use just one semaphore to serialize all
> acces to shared memory, better will be more fine grained.

Best is as fine-grained as possible (which I've tried to do).

David Howells
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.036 / U:0.624 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site