From: arrao@cdac.in (Raghavendra)
To: kernelnewbies@lists.kernelnewbies.org
Subject: KGPU : any scope?
Date: Mon, 01 Dec 2014 13:25:57 +0530 [thread overview]
Message-ID: <547C1F0D.9040801@cdac.in> (raw)
Hello all,
I was going through the concept of KGPU, which is a GPU computing
framework for the Linux Kernel. I've read the white paper on it(can be
found at http://www.cs.utah.edu/~wbsun/kgpu.pdf) and I am very much
interested in this project, but what could be the scope of
this(although, the paper mentions a few application areas like crypto,
networking, fs, etc)? Does the kernel really require GPU's assistance?
What is the scope of building kernel frameworks around it?
Also the current framework is build using CUDA. I want to re-implement
the same using OpenCL as it is supported by most of the GPUs. As per my
perspective, I see a huge learning opportunity here. But, practically
how fas is it useful?
Any suggestions would be helpful.
Thanks
Raghavendra.
-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------
reply other threads:[~2014-12-01 7:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=547C1F0D.9040801@cdac.in \
--to=arrao@cdac.in \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.