I set PCIe 3.0 permanently.
With a system of 150K atoms there is no acceleration at all of molecular
dynamics with ivy with respect to sandy bridge.
At the end of this exercise, given the very meager acceleration with 500K
atoms (which is a large system under any respect, even for supercomputers)
On Mon, Nov 18, 2013 at 10:39:53PM +0100, Francesco Pietra wrote:
> I forgot to mention that LnkSta 8GT/s is obtained only when actually
> carrying out the MD simulation.
I believe to save power the link speed changes on the fly based on demand.
--
Len Sorensen
--
To UNSUBSCRIBE, email to deb
I forgot to mention that LnkSta 8GT/s is obtained only when actually
carrying out the MD simulation.
fp
-- Forwarded message --
From: Francesco Pietra
Date: Mon, Nov 18, 2013 at 10:37 PM
Subject: Re: Fwd: upgrade to jessie from wheezy with cuda problems
To: Lennart Sorensen
Cc
>
> Might need nvidia-current instead of nvidia.
It failed to bring to PCIe 3.0 when inserted into nvidia.conf
francesco@gig64:/etc/modprobe.d$ cat nvidia.conf
alias nvidia nvidia-current
remove nvidia-current rmmod nvidia
# 1. options nvidia-current NVreg_EnablePCIeGen3=1
(of course it was not
On Sun, Nov 17, 2013 at 10:45:58AM +0100, Francesco Pietra wrote:
> I am attacking the problem from another side, directly from within the OS
> itself:
>
> #lspi -
>
> tells that the link speed (= link status) "LnkSta" is at 5Gb/s, no matter
> whether the system is at number crunching or not.
Em 18-11-2013 13:13, Francesco Pietra escreveu:
It is getting hard, unless I mistaken what was suggested by nvidia .
Thus, following what was suggested by nvidia as a no-barrier solution,
https://devtalk.nvidia.com/default/topic/545186/enabling-pcie-3-0-with-nvreg_enablepciegen3-on-titan/?offset
Em 18-11-2013 13:13, Francesco Pietra escreveu:
It is getting hard, unless I mistaken what was suggested by nvidia .
Thus, following what was suggested by nvidia as a no-barrier solution,
https://devtalk.nvidia.com/default/topic/545186/enabling-pcie-3-0-with-nvreg_enablepciegen3-on-titan/?offset
nvidia
suggestion on internet.
francesco pietra
-- Forwarded message --
From: Francesco Pietra
Date: Sun, Nov 17, 2013 at 4:09 PM
Subject: Fwd: upgrade to jessie from wheezy with cuda problems
To: amd64 Debian , Lennart Sorensen <
lsore...@csclub.uwaterloo.ca>
This addendu
t 11:42 AM
Subject: Fwd: upgrade to jessie from wheezy with cuda problems
To: amd64 Debian , Lennart Sorensen <
lsore...@csclub.uwaterloo.ca>
Very sorry, forget about previous post. There, I had started MD from the
gnome terminal, without activating the GPUUs.
When carrying out regularly M
and LnkSta are 5GT/s, as from PCIe
2.0.
Thus, the problem seems to be activating PCIe 3.0, as before said.
francesco pietra
-- Forwarded message --
From: Francesco Pietra
Date: Sun, Nov 17, 2013 at 11:29 AM
Subject: Fwd: upgrade to jessie from wheezy with cuda problems
To: amd64
])
Subsystem: NVIDIA Corporation Device 0969
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
Date: Tue, Nov 12, 2013 at 3:54 PM
Subject: upgrade to jessie from whe
I am attacking the problem from another side, directly from within the OS
itself:
#lspi -
tells that the link speed (= link status) "LnkSta" is at 5Gb/s, no matter
whether the system is at number crunching or not. I.e., my system is at
PCIe 2.0. This might explain why upgrading from sandy bri
On Wed, Nov 13, 2013 at 05:43:47PM -0500, Lennart Sorensen wrote:
> On Wed, Nov 13, 2013 at 10:53:30PM +0100, Francesco Pietra wrote:
> > francesco@gig64:~/tmp$ file ./CUDA-Z-0.7.189.run
> > ./CUDA-Z-0.7.189.run: data
> > francesco@gig64:~/tmp$
>
> OK that's weird. I expected to see x86 32 or 64b
On Wed, Nov 13, 2013 at 10:53:30PM +0100, Francesco Pietra wrote:
> francesco@gig64:~/tmp$ file ./CUDA-Z-0.7.189.run
> ./CUDA-Z-0.7.189.run: data
> francesco@gig64:~/tmp$
OK that's weird. I expected to see x86 32 or 64bit binary.
Seems to be a shell scripts with compressed code in it. Yuck. :)
>
> What does 'file ./CUDA-Z-0.7.189.run' say?
>
francesco@gig64:~/tmp$ file ./CUDA-Z-0.7.189.run
./CUDA-Z-0.7.189.run: data
francesco@gig64:~/tmp$
On Wed, Nov 13, 2013 at 7:52 PM, Lennart Sorensen <
lsore...@csclub.uwaterloo.ca> wrote:
> On Wed, Nov 13, 2013 at 07:40:10PM +0100, Francesco Pi
francesco@gig64:~$ file
/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z
/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z: ERROR: cannot open
`/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z' (No such file or
directory)
francesco@gig64:~$
On Wed, Nov 13, 2013 at 8:18 PM, Fabricio
Em 13-11-2013 16:40, Francesco Pietra escreveu:
francesco@gig64:~/tmp$ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/
francesco@gig64:~/tmp$ ./CUDA-Z-0.7.189.run
CUDA-Z 0.7.189 Container
Starting CUDA-Z...
/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z: error while
loading shared libra
On Wed, Nov 13, 2013 at 07:40:10PM +0100, Francesco Pietra wrote:
> francesco@gig64:~/tmp$ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/
That is unnecesary. That is already in the library path. The local
directory is not. Windows implicitly looks in the current directory
for files, linux (a
bandwidth.
thanks
francesco pietra
-- Forwarded message --
From: Francesco Pietra
Date: Wed, Nov 13, 2013 at 7:40 PM
Subject: Fwd: upgrade to jessie from wheezy with cuda problems
To: amd64 Debian
francesco@gig64:~/tmp$ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu
francesco@gig64:~/tmp$
-- Forwarded message --
From: Francesco Pietra
Date: Wed, Nov 13, 2013 at 10:32 AM
Subject: Re: upgrade to jessie from wheezy with cuda problems
To: Lennart Sorensen
Cc: amd64 Debian
My answer seems to have disappeared. I summarize here.
"mo
On Wed, Nov 13, 2013 at 10:32:26AM +0100, Francesco Pietra wrote:
> My answer seems to have disappeared. I summarize here.
>
> "modinfo nvidia-curred" works well. CUDA libraries are installed.
>
> For nvidia-cuda-toolkit, nvidia offers SDK packages for Ubuntu, not for
> Debian. I don't like to g
On Wed, Nov 13, 2013 at 10:13:15AM +0100, Francesco Pietra wrote:
> >
> > I think it was renamed. No idea why. modinfo nvidia-current should
> > work though.
>
> Yes, it does.
>
> Do you have the cuda libraries for the 319 version installed?
>
> Yes
>
>
> I don't play around with GPU comput
My answer seems to have disappeared. I summarize here.
"modinfo nvidia-curred" works well. CUDA libraries are installed.
For nvidia-cuda-toolkit, nvidia offers SDK packages for Ubuntu, not for
Debian. I don't like to get into troubles with Ubuntu, which, unlike
LinuxMINT, is not compatible with
>
> I think it was renamed. No idea why. modinfo nvidia-current should
> work though.
Yes, it does.
Do you have the cuda libraries for the 319 version installed?
Yes
I don't play around with GPU computations, but from what I have read it
> does need a certain size job before the overhead of
On Tue, Nov 12, 2013 at 10:35:53PM +0100, Francesco Pietra wrote:
> # apt-get --purge remove *legacy*
> did the job.
>
> I wonder how these legacy packages entered the scene while
> updating/upgrading from a clean wheezy.
>
> The bad news are that with the new driver 319.60 there was no accelerat
# apt-get --purge remove *legacy*
did the job.
I wonder how these legacy packages entered the scene while
updating/upgrading from a clean wheezy.
The bad news are that with the new driver 319.60 there was no acceleration
of molecular dynamics for a job of modest size (150K atoms) and slight
accel
On Tue, Nov 12, 2013 at 05:22:18PM +0100, Francesco Pietra wrote:
> Yes. Also,
>
> # apt-get remove nvidia-kernel-dkms
>
> # apt-get install nvidia-kernel-dkms
>
> (which, in the year 2011, served to clear the driver at
> /lib/modules/2.6.38-2-amd64/updates/dkms. But now the kernel was 3.2.) lef
Yes. Also,
# apt-get remove nvidia-kernel-dkms
# apt-get install nvidia-kernel-dkms
(which, in the year 2011, served to clear the driver at
/lib/modules/2.6.38-2-amd64/updates/dkms. But now the kernel was 3.2.) left
the issue unaltered.
# modinfo nvidia
ERROR: module nvidia not found
$ dpkg
On Tue, Nov 12, 2013 at 03:54:32PM +0100, Francesco Pietra wrote:
> Hello:
> I decided to try jessie to get PCIe 3.0 with a recent nvidia driver, thus
> upgrading from wheezy.
>
> wheezy was
> uname -r
> 3.2.0-4-amd64
>
> nvidia-smi
> 304.88
>
> nvcc --version
> 4.2
>
> (the latter is also the
Hello:
I decided to try jessie to get PCIe 3.0 with a recent nvidia driver, thus
upgrading from wheezy.
wheezy was
uname -r
3.2.0-4-amd64
nvidia-smi
304.88
nvcc --version
4.2
(the latter is also the version at which the molecular dynamics code was
compiled, and used without calling the X-server
30 matches
Mail list logo