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

[Feature] Support CARAFE with Cambricon MLU backend #2087

Closed
wants to merge 5 commits into from
Closed

[Feature] Support CARAFE with Cambricon MLU backend #2087

wants to merge 5 commits into from

Conversation

zcyKTH
Copy link
Contributor

@zcyKTH zcyKTH commented Jun 30, 2022

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.

Motivation

The motivation of the PR is to support running CARAFE with Cambricon MLU backend.

It includes three parts:

Add carafe_mlu_kernel.mlu src code as MLU kernel.
Add carafe_mlu.cpp to support launching kernel in PyTorch.
Refactor test_carafe.py to support allclose check.

Modification

MLU src code
Add MLU src code of CARAFE in directory mmcv/ops/csrc/common/mlu/carafe_mlu_kernel.mlu.
PyTorch adaptation
Adapt CARAFE for PyTorch in mmcv/ops/csrc/pytorch/mlu/carefe_mlu.cpp.
Common functions
Add IO functions with 2D/3D pattern in mmcv/ops/csrc/common/mlu/common_mlu_helper.hpp.
Unit test
Add baseline in tests/data/for_carafe and support test CARAFE with various backends in tests/test_ops/test_carafe.py.

BC-breaking (Optional)

Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.

Use cases (Optional)

If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.

Checklist

Before PR:

  • I have read and followed the workflow indicated in the CONTRIBUTING.md to create this PR.
  • Pre-commit or linting tools indicated in CONTRIBUTING.md are used to fix the potential lint issues.
  • Bug fixes are covered by unit tests, the case that causes the bug should be added in the unit tests.
  • New functionalities are covered by complete unit tests. If not, please add more unit test to ensure the correctness.
  • The documentation has been modified accordingly, including docstring or example tutorials.

After PR:

  • If the modification has potential influence on downstream or other related projects, this PR should be tested with some of those projects, like MMDet or MMCls.
  • CLA has been signed and all committers have signed the CLA in this PR.

@grimoire
Copy link
Member

grimoire commented Jul 5, 2022

Please update the unit test.

@zcyKTH
Copy link
Contributor Author

zcyKTH commented Jul 14, 2022

Please update the unit test.

Done

@zhouzaida zhouzaida reopened this Jul 19, 2022
Copy link
Member

@grimoire grimoire left a comment

Choose a reason for hiding this comment

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

@zhouzaida
Copy link
Collaborator

closed by #2212

@zhouzaida zhouzaida closed this Aug 18, 2022
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.

4 participants