How can an EE major looking to get into HPC bolster their CS foundation? Post: 302910330

Sponsored Content

Special Forums UNIX and Linux Applications High Performance Computing How can an EE major looking to get into HPC bolster their CS foundation? Post 302910330 by figaro on Wednesday 23rd of July 2014 03:44:54 PM

07-23-2014

Registered User

Watching some youtube videos on supercomputing is always a good way to follow the current trends.
Most of our client base uses C# for computing large scale calculation applications. But for the true heavy-duty computations there is really no alternative to C++ on Linux, including from a career perspective. So you will probably delve into g++ and possibly also clang for the extra debugging messages.
A solid understanding of how databases operate and a ready knowledge of how database performance can be increased is also required.
Finally, if you have an nVidia GPU card, there is CUDA for parallelising your application. Else - going really high end - you may have a coprocessor from Intel, such as the Xeon Phi. That in turn requires its own Intel compiler / debugger, which also readily supports parallelism.

figaro

View Public Profile for figaro

Find all posts by figaro

6 More Discussions You Might Find Interesting

1. High Performance Computing

HPC Related Links

Our directory of HPC related links is growing: Virtualization, Grid and Cloud Computing - Links Please contribute!

2. High Performance Computing

Guides for new HPC admins

In my company, it's fallen on me to serve as the admin of our new HPC cluster, a task that's very new to me. It's very important to me to lay a solid foundation and avoid any unnecessary pitfalls. So, can anyone recommend a succinct guide or list of do's-and-don'ts for adiminstering an HPC cluster?...

3. High Performance Computing

How to check performance of your HPC cluster?

Hello Everybody, I have few queries : Do you have any idea how to check the performance of HPC cluster having mpich on top of centos 6.2? Are there any standard programs (like FFT, graphics rendering etc) to check the performance of mpi cluster with single node and multiple nodes? Can we...

4. High Performance Computing

HPC Linpack test

Hi, I compiled Linpack with ATLAS for test. What other libraries except ATLAS can be used to test?

5. Homework & Coursework Questions

Class hpc project

My high school started a tech lab where students like myself can take apart computers, build circuit boards, learn to program and lots more. I got the job of building a cluster with 4 old work stations we have. This is just a trial if it works well we can get more work stations. We have one...

6. High Performance Computing

Helpful Ressources for HPC Admin

Hi Everyone I am new to this valuable forum and would like to ask members for some helpful resources to learn HPC administration and monitoring resources such as webinars, websites, forums, books, and moocs as I need them to get more competencies to my career. Thanks

LEARN ABOUT SUSE

gnu_dev_major

MAKEDEV(3)						     Linux Programmer's Manual							MAKEDEV(3)

NAME

       makedev, major, minor - manage a device number

SYNOPSIS

       #define _BSD_SOURCE
       #include <sys/types.h>

       dev_t makedev(int maj, int min);

       int major(dev_t dev);
       int minor(dev_t dev);

DESCRIPTION

       A  device  ID  consists of two parts: a major ID, identifying the class of the device, and a minor ID, identifying a specific instance of a
       device in that class.  A device ID is represented using the type dev_t.

       Given major and minor device IDs, makedev() combines these to produce a device ID, returned as the function result.  This device ID can	be
       given to mknod(2), for example.

       The  major() and minor() functions perform the converse task: given a device ID, they return, respectively, the major and minor components.
       These macros can be useful to, for example, decompose the device IDs in the structure returned by stat(2).

CONFORMING TO

       The makedev() major() and minor() functions are not specified in POSIX.1, but are present on many other systems.

NOTES

       These interfaces are defined as macros.	Since glibc 2.3.3, they have been aliases for three  GNU-specific  functions:  gnu_dev_makedev(3),
       gnu_dev_major(3), and gnu_dev_minor(3).	The latter names are exported, but the traditional names are more portable.

SEE ALSO

       mknod(2), stat(2)

COLOPHON

       This  page is part of release 3.25 of the Linux man-pages project.  A description of the project, and information about reporting bugs, can
       be found at http://www.kernel.org/doc/man-pages/.

Linux								    2008-12-01								MAKEDEV(3)