Skip to content
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

nv_full: #MACs and precision #88

Closed
ratnayak opened this issue Jan 17, 2018 · 4 comments
Closed

nv_full: #MACs and precision #88

ratnayak opened this issue Jan 17, 2018 · 4 comments

Comments

@ratnayak
Copy link

  1. its stated that nv_full is multi-precision. does it mean we can program the precision selection--int8b, int16n or fp16b--after HW implementation?

  2. also its stated that nv_full has 2048 MACs (precision not specified). if run under fp16b does it has 2048 or 1024 fp16b MACs?

thanks
Ruwan

@jwise
Copy link
Contributor

jwise commented Jan 23, 2018

Yes, this is programmable at runtime -- I believe you get 2048 MACs, no matter what precision you select.

@jwise
Copy link
Contributor

jwise commented Jan 23, 2018

(Closing this issue for now -- feel free to reopen if needed.)

@jwise jwise closed this as completed Jan 23, 2018
@ratnayak
Copy link
Author

there is only 1024 instentiations of NV_NVDLA_CMAC_CORE_MAC_mul module for nv_full.
so same question but perhaps in a different form: A single instentiation of NV_NVDLA_CMAC_CORE_MAC_mul module in nv_full--can it be programmed to do two int8b-MACs or a single int16b-MACs based on the reg2dp_proc_precision setting?
Thanks.

@jwise jwise mentioned this issue Jan 25, 2018
@jwise
Copy link
Contributor

jwise commented Jan 25, 2018

In fact, I was in error, as you have noted: to be clear, fp16 is 1024 MACs, and int8 is 2048 MACs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants