From: Paul Menzel <pmenzel@molgen.mpg.de>
To: linux-raid@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-accelerators@lists.ozlabs.org,
linux-nvme@lists.infradead.org
Subject: Using aGPU for RAID calculations (proprietary GRAID SupremeRAID)
Date: Tue, 30 Nov 2021 12:58:10 +0100 [thread overview]
Message-ID: <ccdbb0d7-d043-d41f-508b-4a464ffa5fe9@molgen.mpg.de> (raw)
Dear Linux folks,
I read about GRAID SupremeRAID [1], which seems to be an Nvidia T1000
card and software to use the card for RAID calculations.
> GRAID SupremeRAID works by installing a virtual NVMe controller onto
> the operating system and integrating a PCIe device into the system
> equipped with a high-performance AI processor to handle all RAID
> operations of the virtual NVMe controller
According to the review *GRAID SupremeRAID SR-1000 Review* [2] it
performs quite well. I couldn’t find any driver files online.
Now I am wondering, why a graphics card seems to help so much. What
operations are there, modern CPUs cannot keep up with?
If GPUs are that much better, are people already working on a FLOSS
solution for the Linux kernel, so people can “just” plug in a graphics
card to increase the speed?
Does the Linux kernel already have an API to offload calculations to
accelerator cards, so it’s basically plug and play (with AMD graphics
cards for example using HSA/KFD)? Entropy sources, like the ChaosKey
[3], work like that. If not, would the implementation go under `lib/raid6`?
Kind regards,
Paul
[1]:
https://www.graidtech.com/post/graid-reveals-the-next-generation-of-enterprise-data-protection-nvme-ssds
[2]: https://www.storagereview.com/review/graid-supremeraid-sr-1000-review
[3]: https://altusmetrum.org/ChaosKey/
next reply other threads:[~2021-11-30 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 11:58 Paul Menzel [this message]
2021-11-30 14:46 ` Using aGPU for RAID calculations (proprietary GRAID SupremeRAID) Wolfgang Denk
2021-11-30 16:20 ` Piergiorgio Sartor
2022-12-08 21:42 ` Janpieter Sollie
2021-11-30 16:46 ` Keith Busch
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=ccdbb0d7-d043-d41f-508b-4a464ffa5fe9@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=linux-accelerators@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-raid@vger.kernel.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.