usrse.github.io icon indicating copy to clipboard operation
usrse.github.io copied to clipboard

Update skills.md

Open wsphd opened this issue 2 years ago • 9 comments

Added FPGA to GPU Programming

Description

Added FPGA to GPU Programming

Motivation and Context

This adds more granularity and detail to hardware-level programming.

Checklist:

  • [ ] I have posted the link for the PR in the usrse slack (#website) to ask for reviewers
  • [ ] I have previewed changes locally
  • [ ] I have updated the README.md if necessary

cc @usrse-maintainers

wsphd avatar Jan 05 '23 01:01 wsphd

I'm not an exert on this, but should it be its own point or are those two things (GPU and FPGA) typically listed together?

jdamerow avatar Jan 05 '23 13:01 jdamerow

Thanks for the addition @wsphd! We clearly missed FPGAs. I'd vote to list FPGA as a separate item. The small number of people I know that do FPGA work, also do GPU (and are quite knowledgable in both), but the reverse isn't necessarily true. It seems unique enough we could list it separately. And we should list it, it's clearly a growing area.

cosden avatar Jan 05 '23 14:01 cosden

I am good with listing FPGA as a separate item.

JeffCarver avatar Jan 05 '23 16:01 JeffCarver

All,

I just listed the two together in the interest of terseness over verbosity given this audience.  Also, as a new member, I wasn't sure what the posture was for this group in general and these documentation elements specifically.

I've got several more additions as well.  What's the favor of the group?  Do a separate PR for each or batch them together as one PR?

Best,

Wayne

On 1/5/2023 8:53 AM, JeffCarver wrote:

I am good with listing FPGA as a separate item.

— Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_USRSE_usrse.github.io_pull_1038-23issuecomment-2D1372472161&d=DwMCaQ&c=Oo8bPJf7k7r_cPTz1JF7vEiFxvFRfQtp-j14fFwh71U&r=arUOXBJV185ReiAVcorpVCJACrg7Z_StHteKeAMMoBM&m=HfjWWR9dQxCQBHAK9sfzk6FINRcMc4YiFRXRwMwLbqOauvSJP88rWukS7G0YgQ24&s=Qz7b-IiNDZt9d9CGx1tLDMA3V95UFoRZY5QEyNi40Gw&e=, or unsubscribe https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAN7WWEK364AWRC27APMPBDWQ34CDANCNFSM6AAAAAATRMR6KY&d=DwMCaQ&c=Oo8bPJf7k7r_cPTz1JF7vEiFxvFRfQtp-j14fFwh71U&r=arUOXBJV185ReiAVcorpVCJACrg7Z_StHteKeAMMoBM&m=HfjWWR9dQxCQBHAK9sfzk6FINRcMc4YiFRXRwMwLbqOauvSJP88rWukS7G0YgQ24&s=xjJpKoZh8Div3vE3xtYPlOQ-2p_Dl9oRivKrECidnEo&e=. You are receiving this because you were mentioned.Message ID: @.***>

wsphd avatar Jan 05 '23 17:01 wsphd

Thank you for the contribution! I think adding FGPA as a separate item would be worthwhile. Since FGPA is less familiar as an acronym than GPU, would it be helpful to spell out the full name?

I've got several more additions as well. What's the favor of the group? Do a separate PR for each or batch them together as one PR?

That sounds great! My inclination would be to batch them together as a single PR.

namurphy avatar Jan 05 '23 18:01 namurphy

Nick,

A compromise might be to just link it to the Wikipedia page (or similar) for the acronym but that approach is true for many other elements as well.

Wayne

On 1/5/2023 10:37 AM, Nick Murphy wrote:

Thank you for the contribution! I think adding FGPA as a separate item would be worthwhile. Since FGPA is less familiar as an acronym than GPU, would it be helpful to spell out the full name?

I've got several more additions as well. What's the favor of the
group? Do a separate PR for each or batch them together as one PR?

That sounds great! My inclination would be to batch them together as a single PR.

— Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_USRSE_usrse.github.io_pull_1038-23issuecomment-2D1372590990&d=DwMCaQ&c=Oo8bPJf7k7r_cPTz1JF7vEiFxvFRfQtp-j14fFwh71U&r=arUOXBJV185ReiAVcorpVCJACrg7Z_StHteKeAMMoBM&m=VcWRKX82UdKnfTXAe0U36JnLynWtArMJBdyaO7qls_AiD0SDMBDOnz2SYSuPpc06&s=szS2PvHeC6R8lxsHfWBmGSf6_ATZqSNJP26gL5cwJQ8&e=, or unsubscribe https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAN7WWHZCT6CETP6CER52QDWQ4IGVANCNFSM6AAAAAATRMR6KY&d=DwMCaQ&c=Oo8bPJf7k7r_cPTz1JF7vEiFxvFRfQtp-j14fFwh71U&r=arUOXBJV185ReiAVcorpVCJACrg7Z_StHteKeAMMoBM&m=VcWRKX82UdKnfTXAe0U36JnLynWtArMJBdyaO7qls_AiD0SDMBDOnz2SYSuPpc06&s=Qvq7Dv0hhPwnRxP0HosSytRtvKjvLMd_wHY3d2uEW8I&e=. You are receiving this because you were mentioned.Message ID: @.***>

wsphd avatar Jan 05 '23 18:01 wsphd

Nick, A compromise might be to just link it to the Wikipedia page (or similar) for the acronym but that approach is true for many other elements as well.

I had actually begun to think the same thing! Having Wikipedia links for less well known items on the list could be potentially quite helpful.

namurphy avatar Jan 05 '23 20:01 namurphy

I really like the suggestion of linking to wikipedia pages! Great idea. @wsphd want to make FPGA a separate entry (I think being verbose is fine!) and add more (either in this PR or in a new one, whatever is easier)?

cosden avatar Jan 25 '23 03:01 cosden

Hi all - this seems to have gone a bit stale. @wsphd would you still like to complete this? It looks like folks decided on

  1. having separate list items
  2. linking to Wikipedia (at least for these new entries)

I think adding other links can be a separate PR

kescobo avatar Jun 18 '23 14:06 kescobo