Wine support 4core CPU?
Wine support 4core CPU?
Wine support Intel quad-core cpu?
Thank you.
Thank you.
Wine support 4core CPU?
On Wed, May 14, 2008 at 1:15 PM, psychok9 <[email protected]> wrote:
John
Yes wine supports whatever amount of cpu cores you have.Wine support Intel quad-core cpu?
Thank you.
John
Wine support 4core CPU?
John Drescher wrote:
James McKenzie
It only uses on core at a time. There is an issue referencing this.On Wed, May 14, 2008 at 1:15 PM, psychok9 <[email protected]> wrote:
Yes wine supports whatever amount of cpu cores you have.Wine support Intel quad-core cpu?
Thank you.
John
James McKenzie
Re: Wine support 4core CPU?
Wrong.James McKenzie wrote:It only uses on core at a time. There is an issue referencing this.
Wine uses everythin available to the system. If your system sees all those 4 cores, then Wine will happily use all those 4 cores.
Re: Wine support 4core CPU?
Great! I want buy 4Core Intel cpu for maximize my WOW performance on Linux and play and relax without drop-down of frameratesvitamin wrote:Wrong.James McKenzie wrote:It only uses on core at a time. There is an issue referencing this.
Wine uses everythin available to the system. If your system sees all those 4 cores, then Wine will happily use all those 4 cores.
I've an 8800 GT and Wine use OpenGL library.
Re: Wine support 4core CPU?
And why do you think it will be faster then 1 or 2 core? You have not asked about game performance. You asked "can Wine use?" - yes it can. But depends.psychok9 wrote:Great! I want buy 4Core Intel cpu for maximize my WOW performance on Linux and play and relax without drop-down of frameratesvitamin wrote:Wrong.James McKenzie wrote:It only uses on core at a time. There is an issue referencing this.
Wine uses everythin available to the system. If your system sees all those 4 cores, then Wine will happily use all those 4 cores.
I've an 8800 GT and Wine use OpenGL library.
Wine coded in a way that it can use only one CPU/core for d3d/opengl/GUI at one given time. Besides most games won't benefit from all those extra cores running around. 2 faster CPUs/cores are better then 4 slower ones.
Wine support 4core CPU?
On Fri, May 16, 2008 at 2:18 PM, Sleaka J <[email protected]> wrote:
John
It is but it does not make good use of more than one core even on windows.I didn't think World of Warcraft was multi-threaded.
John
Wine support 4core CPU?
vitamin wrote:
happily use one Core (as it does here) and leave the rest of the system
for other applications. I've run 99.5% on one program with the other
core left alone. Maybe, I'm reading that incorrectly then. BTW, I have
an Intel Duo Core on my system here.
James McKenzie
Is Wine cleanly multi-threaded? I did not think it was. Thus it willJames McKenzie wrote:
Wrong. [Exclamation]It only uses on core at a time. There is an issue referencing this.
Wine uses everythin available to the system. If your system sees all those 4 cores, then Wine will happily use all those 4 cores.
happily use one Core (as it does here) and leave the rest of the system
for other applications. I've run 99.5% on one program with the other
core left alone. Maybe, I'm reading that incorrectly then. BTW, I have
an Intel Duo Core on my system here.
James McKenzie
Re: Wine support 4core CPU?
Well yes it uses posix threads when they are available (most platforms now days).James McKenzie wrote:Is Wine cleanly multi-threaded?
The only two bottlenecks I can think of - wineserver and x11lock. Wineserver is single-threaded. And x11lock - used to limit all communications with X11 server to one thread at a time.
Wine support 4core CPU?
vitamin wrote:
MacOSX is not POSIX thread compliant.
This old dog is never too old to learn new tricks.
James McKenzie
Thank you for clearing this up. As I stated I have two cores and maybeJames McKenzie wrote:
Well yes it uses posix threads when they are available (most platforms now days).Is Wine cleanly multi-threaded?
MacOSX is not POSIX thread compliant.
Maybe that is where I got the one-thread for Wine from.The only two bottlenecks I can think of - wineserver and x11lock. Wineserver is single-threaded. And x11lock - used to limit all communications with X11 server to one thread at a time.
This old dog is never too old to learn new tricks.
James McKenzie
Wine support 4core CPU?
On Saturday 17 May 2008 03:58:01 pm ulberon wrote:
additional work to a core grinding on something heavy? If not, what benefit
would second-guessing the scheduler bring?
--
Paul Johnson
[email protected]
Explaination of .pgp part: http://linuxmafia.com/faq/Mail/rant-gpg.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://www.winehq.org/pipermail/wine-us ... chment.pgp
Am I wrong in thinking that the Linux scheduler is smart enough to not assignHas wine bothered messing with CPU affinity? For instance, binding all
other wine processes and threads to other cores, cores that the
GUI/OpenGL/D3D is not running on?
additional work to a core grinding on something heavy? If not, what benefit
would second-guessing the scheduler bring?
--
Paul Johnson
[email protected]
Explaination of .pgp part: http://linuxmafia.com/faq/Mail/rant-gpg.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://www.winehq.org/pipermail/wine-us ... chment.pgp
Just based on some limited testing, yes, you are incorrect in thinking that the Linux Scheduler is smart enough not to assign additional work. It passes the process around the cores like a party favor.
I was just curious if anyone pursued it, there are performance benefits to binding a process to a specific core (in the general case), increased cache hits being one. To cut to the chase, I think there would be performance benefits to binding the opengl/d3d process to a core, and binding the other processes to the remaining cores.
I was just curious if anyone pursued it, there are performance benefits to binding a process to a specific core (in the general case), increased cache hits being one. To cut to the chase, I think there would be performance benefits to binding the opengl/d3d process to a core, and binding the other processes to the remaining cores.