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

[Relay] Expose qnn ops directly from relay.qnn module #15928

Merged
merged 3 commits into from Oct 17, 2023

Conversation

quic-sanirudh
Copy link
Contributor

When we access nn ops in relay, we can directly access them as relay.nn.<op> where <op> can be any nn op like conv2d, avg_pool2d, etc.

When we access qnn ops, we need to access them as relay.qnn.op.<op> as they're not exposed to the relay.qnn module. This change tries to add that.

When we access `nn` ops in relay, we can directly access them as
`relay.nn.<op>` where `<op>` can be any nn op like `conv2d`,
`avg_pool2d`, etc.

When we access `qnn` ops, we need to access them as `relay.qnn.op.<op>`
as they're not exposed to the `relay.qnn` module. This change tries to
add that.
@quic-sanirudh
Copy link
Contributor Author

cc @ibsidorenko

@ibsidorenko
Copy link
Contributor

LGTM. Do you plan to change access names in unit tests?

@quic-sanirudh
Copy link
Contributor Author

LGTM. Do you plan to change access names in unit tests?

Thanks for the review, and yes, I'll update the tests and push it today. Initially I thought it might introduce a lot of changes that hurts git history un-necessarily, but now I think there could be some advantage to doing it (especially since tests are seen as an initial source of example usage of an API).

Copy link
Contributor

@kparzysz-quic kparzysz-quic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks @quic-sanirudh!

@quic-sanirudh quic-sanirudh merged commit 1990315 into apache:main Oct 17, 2023
18 checks passed
@quic-sanirudh quic-sanirudh deleted the expose_qnn_ops_directly branch November 15, 2023 02:38
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

Successfully merging this pull request may close these issues.

None yet

3 participants