-
Notifications
You must be signed in to change notification settings - Fork 439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make Mali GPUs usable (Odroid XU4) #1686
Comments
Is the device attached to SETI@home? Please do so and send me the host ID. |
Here you are: https://setiathome.berkeley.edu/show_host_detail.php?hostid=8122195 Probably more changes will be needed, I have found that there is no dedicated plan class for this GPU - at least I do not see it here: https://boinc.berkeley.edu/trac/wiki/AppPlan |
Is there a science application that utilizes Mali type GPUs? |
I was not able to find one on Internet. Maybe there are some which runs standalone (without BOINC), I did not search for such ones. Yesterday I was able to compile MilkyWay@home for this GPU, however so far I was not able to convince BOINC to give it some work. Today evening I will continue my work, I hope I will be able to make it work. |
You should be able to get work through the anonymous platform feature of BOINC. It's possible that you need to specify the
|
I already tried this but it did not work - I suspect that MilkyWay only checks if GPU type is Nvidia or AMD. Now I am going to pretend that my GPU is an Nvidia one, or if this would not work too I will configure app as an ordinary CPU app. MilkyWay has CPU app version too, so I should be able to get some work this way. |
BTW, I added support for showing the OpenCL GPU on the web page for the host. On 10/25/2016 7:31 AM, sirzooro wrote:
|
Thanks! It should help promoting this new GPU across BOINC projects which already uses other GPUs. |
Any update on this? I checked my computers list at S@H and it still does not display GPUs for these Odroids. |
Oops! I forgot to deploy scheduler modes on S@h.
Will be done by tomorrow.
-- D
…On 12/28/2016 10:00 AM, sirzooro wrote:
Any update on this? I checked my computers list at ***@***.*** and it still does not
display GPUs for these Odroids.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1686 (comment)>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AA8KgevdvGwagHW0P2FWk2Df0IgpzBnrks5rMqOrgaJpZM4KfK8e>.
|
Thanks! I see that is is displayed now:
I wonder if these two entries should stay as-is, or maybe collapse them into one with Please also add OpenCL version, it is displayed for my Nvidia cards. This would be useful for project owners to determine which OpenCL version is supported by majority of GPUs on various platforms. |
Something is wrong with generic support for OpenCL devices. I was able to run Xansons on this GPU. However BOINC uses only one of GPUs, while it should use both of them. <use_all_gpus> in cc_config.xml set to 1 did not help. I also tried to stop all CPU tasks to make sure that they do not get into way, but this did not work too. I tested this on Boinc 7.6.31. Looks that something is wrong when there are two OpenCL GPUs with the same names but different parameters. |
One more issue: it looks that server ignores both configured jobs limit per GPU, and work buffer size reported by client in scheduler request. As a result server sends way too many WUs to client, see link below. This may be related to issue reported by me here few days ago, both server and client probably think that 2nd instance of Mali GPU is idle and try to give it something to work. However this may explain why client asks for more work, but server still should enforce jobs limit. Edit: linked post mentions another issue, peak_flops for GPU on server is set to 0 instead of real value. This should be fixed too. Edit2: another scenario is possible: client requests tasks for 2nd Mali and server thinks the same, but WUs sent ends up in 1st Mali queue. This may lead to endless fetch loop. I also recalled one more issue: public stats pages on server shows stats for Nvidia, AMD and Intel GPUs only. There are no page for Mali, and other vendors who makes GPU chips for ARM. For now all of them could be presented on one new page "Other GPUs". Later in the future they may get separate per-vendor pages as needed. |
I have noticed small cosmetic issue - on task list app name is displayed as "MilkyWay@Home The same name is displayed in WU details. I also saw that Device peak FLOPS for WU is 0.00 GFLOPS. |
I have noticed one thing. When project has app_info.xml which configures app for Mali-T628, client requests tasks for one instance of GPU. When project does not use app_info.xml, client requests tasks for both GPU instances. Here are example lines from event log:
This case probably should be handled in similar way as when computer has two different GPUs from the same vendor (e.g. Nvidia 970 and 1070). |
@sirzooro, is this still an issue? |
is this issiue solved ? or there is any progress about it ? I own some Mali equipped devices (with Rockchip RK3399, it includes Mali-T860MP4/Mali-T864) i get opencl to work on this boards (NanoPi M4 and M4v2 in my case) but i don't get any work from any of ARM projects (exept of yoyo and rakesearch which i did't tested). Have anyone got it to work on non NV/AMD/Intel GPU? |
@markonmoto2, there is no project that has application for GPU on ARM devices. |
I think we should close this issue, as there is no issue. The Client detects Mali GPUs perfectly. |
Detection works properly, but there were other issues. See my comments here starting from #1686 (comment) . Most important one was that BOINC detected two GPUs, but used only one. At this moment I do not run GPU tasks on Odroid, but I may run some extra tests if they will be necessary. |
If they run on odroid, it would be nice to post how did you manage, in order to replicate it also here |
Here are details what I did to run MilkyWay on GPU on Odroid, please take a look: https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4180 I see that last year someone suggested to use <use_all_gpus>1</use_all_gpus> param. This may explain why BOINC used only one GPU instance instead of both, it needs to be confirmed. |
@sirzooro Could you make a detailed description of how you were abled to run on the gpu, so that hopefully boinc can also incorporate your setup to eventually run it also on a android phone? |
OK. I do not remember all details, but it was something like this:
Here is full app_info.xml which I used: <app_info>
<app>
<name>milkyway</name>
<user_friendly_name>MilkyWay@Home</user_friendly_name>
<non_cpu_intensive>0</non_cpu_intensive>
</app>
<file>
<name>milkyway_separation</name>
<executable/>
</file>
<app_version>
<app_name>milkyway</app_name>
<version_num>146</version_num>
<platform>arm-unknown-linux-gnueabihf</platform>
<avg_ncpus>0.0300000</avg_ncpus>
<max_ncpus>0.0300000</max_ncpus>
<plan_class>opencl_nvidia_101</plan_class>
<api_version>7.6.33</api_version>
<file_ref>
<file_name>milkyway_separation</file_name>
<main_program/>
</file_ref>
<coproc>
<type>Mali-T628</type>
<count>1.0</count>
</coproc>
<gpu_ram>268435456.000000</gpu_ram>
<dont_throttle/>
</app_version>
</app_info> |
There were several changes in the client since then. |
I have Odroid XU4, which has OpenCL-capable GPU. It is detected by BOINC client:
I also see following entries in sched_request_*.xml files:
However this is not displayed on Computers page on BOINC project's websites. Please fix this.
The text was updated successfully, but these errors were encountered: