From: Fernando Rodriguez <frodriguez.developer@outlook.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: new computer : any advice ?
Date: Thu, 10 Sep 2015 02:35:08 -0400 [thread overview]
Message-ID: <BLU436-SMTP209E046481211629B80C0D58D510@phx.gbl> (raw)
In-Reply-To: <loom.20150909T230117-94@post.gmane.org>
On Wednesday, September 09, 2015 9:52:55 PM james wrote:
> Jeremi Piotrowski <jeremi.piotrowski <at> gmail.com> writes:
>
> > No, and yes. Compilation is not affected in any way and runtime
> > performance can only be improved _if_ this stuff is explicitly used within
> > the code.
>
> Yes this is all new and a work in progress. I do not think it will be
> gcc-6 that makes the difference in a few years. But folks should be aware
> and look for codes that are accelerated via usage of GPU resources.
> Remember this all started about hardware purchase and future benefits.
> It's definitely not commodity usage atm.
>
>
> > Meaning you would feel a difference in no less then 5 years when gcc-6 is
> > widely used and accelerator support is not restricted to intel MIC and
> > nvidia gpus. James is getting a bit ahead of himself calling this a
> > "game changer" - yeaaaaah... not really right now.
>
> It's not as restricted as you indicate amd, intel, nividia and others like
> arm (Mali and such) are working to support there hardware under the openacc
> code extension now in gcc-5. Granted the more powerful your GPU resources
> are the more they can contribute. This stuff use to only work with
> vendor supplied compilers and sdks, now it's finally available in gcc,
> albeit in it's infancy. Naturally it's going to take a while to
> become mainstream useful; but that more like a year or 2, at most.
The value I see on that technology for desktop computing is that we get the
GPUs for what they're made (graphics processing) but their resources go unused
by most applications, not in buying powerful GPUs for the purpose of offloading
general purpose code, if that's the goal you're better off investing in more
general purpose cores that are more suited for the task.
To trully take advantage of the GPU the actual algorithms need to be rewritten
to use features like SIMD and other advanced parallelization features, most
desktop workloads don't lend themselves for that kind of parallelization. That
is why despite similar predictions about how OpenMP-like parallel models would
obsolete the current threads model since they where first proposed, it hasn't
happened yet.
Even for the purpose of offloading general purpose code, it seems with all the
limitations on OpanACC kernels few desktop applications can take advantage of
it (and noticeably benefit from it) without major rewrites. Off the top of my
head audio, video/graphics encoders, and a few other things that max out the
cpu and can be broken into independent execution units.
--
Fernando Rodriguez
next prev parent reply other threads:[~2015-09-10 6:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 19:56 [gentoo-user] new computer : any advice ? Philip Webb
2015-09-07 20:55 ` Dale
2015-09-08 15:32 ` [gentoo-user] " James
2015-09-08 15:51 ` Stefan G. Weichinger
2015-09-08 16:00 ` Francisco Ares
2015-09-09 2:20 ` James
2015-09-09 18:01 ` Stefan G. Weichinger
2015-09-09 18:24 ` Stefan G. Weichinger
2015-09-09 19:35 ` Jeremi Piotrowski
2015-09-09 20:32 ` Stefan G. Weichinger
2015-09-09 21:52 ` james
2015-09-10 6:35 ` Fernando Rodriguez [this message]
2015-09-10 12:20 ` james
2015-09-10 13:26 ` Rich Freeman
2015-09-10 18:22 ` Gevisz
2015-09-10 21:12 ` james
2015-09-11 4:42 ` Gevisz
2015-09-12 7:49 ` [gentoo-user] Re: OT: GCC 5 Offloading Fernando Rodriguez
2015-09-10 2:22 ` [gentoo-user] Re: new computer : any advice ? james
2015-09-09 19:22 ` Mick
2015-09-09 19:35 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLU436-SMTP209E046481211629B80C0D58D510@phx.gbl \
--to=frodriguez.developer@outlook.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox