Multiple GPU
  1 / 2    
Hi all,
I have 2 GPUs (gtx280) installed on my computer, I want to allocate one of them just for display (as a usual video card) and the other one for CUDA programming and computations, does anybody know how I can do that?
Thanks
Hi all,

I have 2 GPUs (gtx280) installed on my computer, I want to allocate one of them just for display (as a usual video card) and the other one for CUDA programming and computations, does anybody know how I can do that?

Thanks

#1
Posted 10/03/2008 08:29 PM   
alot of people say you have to have an extra monitor hooked up to card #2 but this is false.

if you have the TV-OUT cord that comes with alot of these cards just plug it in the TV-OUT port on back of your cuda card...the other end can be free it dont have to be plugged into anything.

then right click your desktop and select personalize>display settings> and select one of the 4 screens you see to extend the desktop.

on my computer with 2 8800gts screens 1 and 3 goto primary card and screens 2 and 4 goto the 2nd card

i usually select screen 4 and select extend onto this device.
alot of people say you have to have an extra monitor hooked up to card #2 but this is false.



if you have the TV-OUT cord that comes with alot of these cards just plug it in the TV-OUT port on back of your cuda card...the other end can be free it dont have to be plugged into anything.



then right click your desktop and select personalize>display settings> and select one of the 4 screens you see to extend the desktop.



on my computer with 2 8800gts screens 1 and 3 goto primary card and screens 2 and 4 goto the 2nd card



i usually select screen 4 and select extend onto this device.

AMD 64 X2 4200+ @ 2.65ghz
ASUS A8N32-SLI-DELUXE 1405 BETA BIOS
4*512 DDR PC3200
2*8800GTS 512MB G92`S
VISTA PREMIUM 32BIT ALL UPDATES
LATEST DIRECTX (BI-MONTHLY)
LATEST NFORCE DRIVERS
LATEST GFORCE DRIVERS (USUALLY BETA)

#2
Posted 10/03/2008 08:56 PM   
Thanks for your reply,
So, if I connect the monitor to GPU#0, the GPU#1 is completely free, and then by using the cudaSetDevice(1) I can run my CUDA codes on GPU#1 and nothing would be run on GPU#0? am I right?
Thanks for your reply,

So, if I connect the monitor to GPU#0, the GPU#1 is completely free, and then by using the cudaSetDevice(1) I can run my CUDA codes on GPU#1 and nothing would be run on GPU#0? am I right?

#3
Posted 10/03/2008 09:13 PM   
[quote name='kolonel' date='Oct 3 2008, 04:13 PM']Thanks for your reply,
So, if I connect the monitor to GPU#0, the GPU#1 is completely free, and then by using the cudaSetDevice(1) I can run my CUDA codes on GPU#1 and nothing would be run on GPU#0? am I right?
[right][snapback]447417[/snapback][/right]
[/quote]

you forgot to mention the TV-OUT cable that goes into the TV-OUT port on GPU#1 as i previously stated.
[quote name='kolonel' date='Oct 3 2008, 04:13 PM']Thanks for your reply,

So, if I connect the monitor to GPU#0, the GPU#1 is completely free, and then by using the cudaSetDevice(1) I can run my CUDA codes on GPU#1 and nothing would be run on GPU#0? am I right?

[snapback]447417[/snapback]






you forgot to mention the TV-OUT cable that goes into the TV-OUT port on GPU#1 as i previously stated.

AMD 64 X2 4200+ @ 2.65ghz
ASUS A8N32-SLI-DELUXE 1405 BETA BIOS
4*512 DDR PC3200
2*8800GTS 512MB G92`S
VISTA PREMIUM 32BIT ALL UPDATES
LATEST DIRECTX (BI-MONTHLY)
LATEST NFORCE DRIVERS
LATEST GFORCE DRIVERS (USUALLY BETA)

#4
Posted 10/03/2008 09:29 PM   
oops, I forgot...but, I can't understand, why I need that port for the Cuda-GPU (i.e. GPU#1), b/c it's not going to be used for display anytime. :blink:

[quote name='g000fy' date='Oct 3 2008, 01:29 PM']you forgot to mention the TV-OUT cable that goes into the TV-OUT port on GPU#1 as i previously stated.
[right][snapback]447422[/snapback][/right]
[/quote]
oops, I forgot...but, I can't understand, why I need that port for the Cuda-GPU (i.e. GPU#1), b/c it's not going to be used for display anytime. :blink:



[quote name='g000fy' date='Oct 3 2008, 01:29 PM']you forgot to mention the TV-OUT cable that goes into the TV-OUT port on GPU#1 as i previously stated.

[snapback]447422[/snapback]


#5
Posted 10/03/2008 09:45 PM   
No, no, no, a thousand times no. What g000fy said is completely wrong.

You do not have to extend the desktop. Specifically do not extend the desktop. If you extend the desktop the watchdog timer (5s kernel runtime limitation) takes effect.

It will show up as two CUDA devices; one is display, one is not. There's not a really good way to know which is which (it will be one way in Linux and another in Windows), so write a infinite looping kernel and run it on each device. The one that doesn't return an unspecified launch failure 5-10s after starting it is the non-display card. (In Windows, I think it should be device 1 is compute and vice-versa for Linux.)
No, no, no, a thousand times no. What g000fy said is completely wrong.



You do not have to extend the desktop. Specifically do not extend the desktop. If you extend the desktop the watchdog timer (5s kernel runtime limitation) takes effect.



It will show up as two CUDA devices; one is display, one is not. There's not a really good way to know which is which (it will be one way in Linux and another in Windows), so write a infinite looping kernel and run it on each device. The one that doesn't return an unspecified launch failure 5-10s after starting it is the non-display card. (In Windows, I think it should be device 1 is compute and vice-versa for Linux.)

#6
Posted 10/03/2008 09:47 PM   
I didn't connect anything to the GPU#1, and the monitor is connected to GPU#0...So, if at the beginnig of my code I put cudaSetDevice(1), can't I suppose that GPU#1 is fully doing the CUDA computations and GPU#0 is doing the display duties?


[quote name='tmurray' date='Oct 3 2008, 01:47 PM']No, no, no, a thousand times no. What g000fy said is completely wrong.

You do not have to extend the desktop. Specifically do not extend the desktop. If you extend the desktop the watchdog timer (5s kernel runtime limitation) takes effect.

It will show up as two CUDA devices; one is display, one is not. There's not a really good way to know which is which (it will be one way in Linux and another in Windows), so write a infinite looping kernel and run it on each device. The one that doesn't return an unspecified launch failure 5-10s after starting it is the non-display card. (In Windows, I think it should be device 1 is compute and vice-versa for Linux.)
[right][snapback]447429[/snapback][/right]
[/quote]
I didn't connect anything to the GPU#1, and the monitor is connected to GPU#0...So, if at the beginnig of my code I put cudaSetDevice(1), can't I suppose that GPU#1 is fully doing the CUDA computations and GPU#0 is doing the display duties?





[quote name='tmurray' date='Oct 3 2008, 01:47 PM']No, no, no, a thousand times no. What g000fy said is completely wrong.



You do not have to extend the desktop. Specifically do not extend the desktop. If you extend the desktop the watchdog timer (5s kernel runtime limitation) takes effect.



It will show up as two CUDA devices; one is display, one is not. There's not a really good way to know which is which (it will be one way in Linux and another in Windows), so write a infinite looping kernel and run it on each device. The one that doesn't return an unspecified launch failure 5-10s after starting it is the non-display card. (In Windows, I think it should be device 1 is compute and vice-versa for Linux.)

[snapback]447429[/snapback]


#7
Posted 10/03/2008 09:57 PM   
[quote name='kolonel' date='Oct 3 2008, 02:57 PM']I didn't connect anything to the GPU#1, and the monitor is connected to GPU#0...So, if at the beginnig of my code I put cudaSetDevice(1), can't I suppose that GPU#1 is fully doing the CUDA computations and GPU#0 is doing the display duties?
[right][snapback]447436[/snapback][/right]
[/quote]
yes, that is correct.
[quote name='kolonel' date='Oct 3 2008, 02:57 PM']I didn't connect anything to the GPU#1, and the monitor is connected to GPU#0...So, if at the beginnig of my code I put cudaSetDevice(1), can't I suppose that GPU#1 is fully doing the CUDA computations and GPU#0 is doing the display duties?

[snapback]447436[/snapback]




yes, that is correct.

#8
Posted 10/03/2008 10:04 PM   
[quote name='tmurray' date='Oct 3 2008, 05:47 PM']No, no, no, a thousand times no. What g000fy said is completely wrong.

You do not have to extend the desktop. Specifically do not extend the desktop. If you extend the desktop the watchdog timer (5s kernel runtime limitation) takes effect.

It will show up as two CUDA devices; one is display, one is not. There's not a really good way to know which is which (it will be one way in Linux and another in Windows), so write a infinite looping kernel and run it on each device. The one that doesn't return an unspecified launch failure 5-10s after starting it is the non-display card. (In Windows, I think it should be device 1 is compute and vice-versa for Linux.)
[right][snapback]447429[/snapback][/right]
[/quote]
On XP this'll work, but on Vista don't you need both to be display cards? At least that's what's been said here; I run Vista but only 1 card. Also, how do you stop an infinitely looping kernel? (Again, for me it just times out.)
[quote name='tmurray' date='Oct 3 2008, 05:47 PM']No, no, no, a thousand times no. What g000fy said is completely wrong.



You do not have to extend the desktop. Specifically do not extend the desktop. If you extend the desktop the watchdog timer (5s kernel runtime limitation) takes effect.



It will show up as two CUDA devices; one is display, one is not. There's not a really good way to know which is which (it will be one way in Linux and another in Windows), so write a infinite looping kernel and run it on each device. The one that doesn't return an unspecified launch failure 5-10s after starting it is the non-display card. (In Windows, I think it should be device 1 is compute and vice-versa for Linux.)

[snapback]447429[/snapback]




On XP this'll work, but on Vista don't you need both to be display cards? At least that's what's been said here; I run Vista but only 1 card. Also, how do you stop an infinitely looping kernel? (Again, for me it just times out.)

#9
Posted 10/03/2008 10:55 PM   
[quote name='tmurray' date='Oct 3 2008, 04:47 PM']No, no, no, a thousand times no. What g000fy said is completely wrong.

You do not have to extend the desktop. Specifically do not extend the desktop. If you extend the desktop the watchdog timer (5s kernel runtime limitation) takes effect.

It will show up as two CUDA devices; one is display, one is not. There's not a really good way to know which is which (it will be one way in Linux and another in Windows), so write a infinite looping kernel and run it on each device. The one that doesn't return an unspecified launch failure 5-10s after starting it is the non-display card. (In Windows, I think it should be device 1 is compute and vice-versa for Linux.)
[right][snapback]447429[/snapback][/right]
[/quote]

crap i really thought it was that when you were not using SLI enabled.
and to my understanding with cuda using multiple GPU`s you have to have SLI disabled.

with physx in vista this is what you have to do.
with windows XP and LINUX you do not have to do this.

are you sure tmurray that you are correct about this if he is using vista?
[quote name='tmurray' date='Oct 3 2008, 04:47 PM']No, no, no, a thousand times no. What g000fy said is completely wrong.



You do not have to extend the desktop. Specifically do not extend the desktop. If you extend the desktop the watchdog timer (5s kernel runtime limitation) takes effect.



It will show up as two CUDA devices; one is display, one is not. There's not a really good way to know which is which (it will be one way in Linux and another in Windows), so write a infinite looping kernel and run it on each device. The one that doesn't return an unspecified launch failure 5-10s after starting it is the non-display card. (In Windows, I think it should be device 1 is compute and vice-versa for Linux.)

[snapback]447429[/snapback]






crap i really thought it was that when you were not using SLI enabled.

and to my understanding with cuda using multiple GPU`s you have to have SLI disabled.



with physx in vista this is what you have to do.

with windows XP and LINUX you do not have to do this.



are you sure tmurray that you are correct about this if he is using vista?

AMD 64 X2 4200+ @ 2.65ghz
ASUS A8N32-SLI-DELUXE 1405 BETA BIOS
4*512 DDR PC3200
2*8800GTS 512MB G92`S
VISTA PREMIUM 32BIT ALL UPDATES
LATEST DIRECTX (BI-MONTHLY)
LATEST NFORCE DRIVERS
LATEST GFORCE DRIVERS (USUALLY BETA)

#10
Posted 10/03/2008 10:55 PM   
[quote name='g000fy' date='Oct 3 2008, 03:55 PM']are you sure tmurray that you are correct about this if he is using vista?
[right][snapback]447463[/snapback][/right]
[/quote]
Look at where I work. Vista is special because at the moment you can't run CUDA on non-display cards.
[quote name='g000fy' date='Oct 3 2008, 03:55 PM']are you sure tmurray that you are correct about this if he is using vista?

[snapback]447463[/snapback]




Look at where I work. Vista is special because at the moment you can't run CUDA on non-display cards.

#11
Posted 10/03/2008 11:19 PM   
[quote name='tmurray' date='Oct 3 2008, 06:19 PM']Look at where I work. Vista is special because at the moment you can't run CUDA on non-display cards.
[right][snapback]447478[/snapback][/right]
[/quote]

well that is what i said and you said i was wrong.

for vista you have to have a device hooked up to BOTH video cards....that is what i stated.
[quote name='tmurray' date='Oct 3 2008, 06:19 PM']Look at where I work. Vista is special because at the moment you can't run CUDA on non-display cards.

[snapback]447478[/snapback]






well that is what i said and you said i was wrong.



for vista you have to have a device hooked up to BOTH video cards....that is what i stated.

AMD 64 X2 4200+ @ 2.65ghz
ASUS A8N32-SLI-DELUXE 1405 BETA BIOS
4*512 DDR PC3200
2*8800GTS 512MB G92`S
VISTA PREMIUM 32BIT ALL UPDATES
LATEST DIRECTX (BI-MONTHLY)
LATEST NFORCE DRIVERS
LATEST GFORCE DRIVERS (USUALLY BETA)

#12
Posted 10/03/2008 11:24 PM   
Thanks for your help.
My OS is XP64bit; so, I don't have to make both GPUs for display.

And something else...Each GTX280 has 2 dual-link DVI and 1 analog HDTV-out ports. The monitor is connected to one DVI port (in GPU#0), but when I connect the monitor to the other DVI port (in GPU#0), or to the other GPU's (i.e. GPU#1) DVI ports, monitor turns off. If this is normal?
Thanks for your help.

My OS is XP64bit; so, I don't have to make both GPUs for display.



And something else...Each GTX280 has 2 dual-link DVI and 1 analog HDTV-out ports. The monitor is connected to one DVI port (in GPU#0), but when I connect the monitor to the other DVI port (in GPU#0), or to the other GPU's (i.e. GPU#1) DVI ports, monitor turns off. If this is normal?

#13
Posted 10/03/2008 11:55 PM   
[quote name='kolonel' date='Oct 3 2008, 06:55 PM']Thanks for your help.
My OS is XP64bit; so, I don't have to make both GPUs for display.

And something else...Each GTX280 has 2 dual-link DVI and 1 analog HDTV-out ports. The monitor is connected to one DVI port (in GPU#0), but when I connect the monitor to the other DVI port (in GPU#0), or to the other GPU's (i.e. GPU#1) DVI ports, monitor turns off. If this is normal?
[right][snapback]447488[/snapback][/right]
[/quote]

oh you are running XP....well than that does make a difference.

do what tmurray said.
he works for nvidia so you know hes probably got this stuff down pat.
[quote name='kolonel' date='Oct 3 2008, 06:55 PM']Thanks for your help.

My OS is XP64bit; so, I don't have to make both GPUs for display.



And something else...Each GTX280 has 2 dual-link DVI and 1 analog HDTV-out ports. The monitor is connected to one DVI port (in GPU#0), but when I connect the monitor to the other DVI port (in GPU#0), or to the other GPU's (i.e. GPU#1) DVI ports, monitor turns off. If this is normal?

[snapback]447488[/snapback]






oh you are running XP....well than that does make a difference.



do what tmurray said.

he works for nvidia so you know hes probably got this stuff down pat.

AMD 64 X2 4200+ @ 2.65ghz
ASUS A8N32-SLI-DELUXE 1405 BETA BIOS
4*512 DDR PC3200
2*8800GTS 512MB G92`S
VISTA PREMIUM 32BIT ALL UPDATES
LATEST DIRECTX (BI-MONTHLY)
LATEST NFORCE DRIVERS
LATEST GFORCE DRIVERS (USUALLY BETA)

#14
Posted 10/04/2008 12:21 AM   
Please see also the following information:

[url="http://forums.nvidia.com/index.php?showtopic=76946"]http://forums.nvidia.com/index.php?showtopic=76946[/url]
Please see also the following information:



http://forums.nvidia.com/index.php?showtopic=76946

#15
Posted 10/04/2008 03:27 AM   
  1 / 2    
Scroll To Top