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

Support for separation of local buffers to input/weight/output #4

Open
xchen87 opened this issue Nov 1, 2024 · 1 comment
Open

Comments

@xchen87
Copy link

xchen87 commented Nov 1, 2024

Hello,

Looking at the accelerator parsing, neurospector seems to not be able to support separation expression of "LOCAL_BUFFER" if an accelerator maintains separate local buffers to contain input, weight, and output, respectively. Is my understanding correct? if so do you have plan to support, or advise how to express such an architecture?

Thanks in advance.

@pch0561
Copy link
Collaborator

pch0561 commented Nov 11, 2024

Hi,

NeuroSpector supports separate buffers by specifying multiple buffer sizes.
For instance, you can define separate local buffers for input, weight, and output data by specifying multiple values for BUFFER_SIZE (e.g., BUFFER_SIZE=24,448,48). With this configuration, 24 bytes would be allocated for the input buffer, 448 bytes for the weight buffer, and 48 bytes for the output buffer. You can find a specific example of this implementation in the Eyeriss configuration file at configs/accelerators/eyeriss.cfg.
Additionally, this separated buffer expression is not limited to LOCAL_BUFFER - it can be applied to any temporal component in the architecture.

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