Skip to content

Conversation

@dzdang
Copy link
Contributor

@dzdang dzdang commented Mar 9, 2022

Stack from ghstack (oldest at bottom):

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:

python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn

Differential Revision: D34995805

…Conv.cpp to an utilities file

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Mar 9, 2022

CI Flow Status

⚛️ CI Flow

Ruleset - Version: v1
Ruleset - File: https://github.com/pytorch/pytorch/blob/470167313b7641468496764013e9c7a16e325ea5/.github/generated-ciflow-ruleset.json
PR ciflow labels: ciflow/default
Add ciflow labels to this PR to trigger more builds:

Workflows Labels (bold enabled) Status
Triggered Workflows
linux-binary-conda ciflow/binaries, ciflow/binaries_conda, ciflow/default ✅ triggered
linux-binary-libtorch-cxx11-abi ciflow/all, ciflow/binaries, ciflow/binaries_libtorch, ciflow/default, ciflow/trunk ✅ triggered
linux-binary-libtorch-pre-cxx11 ciflow/all, ciflow/binaries, ciflow/binaries_libtorch, ciflow/default, ciflow/trunk ✅ triggered
linux-binary-manywheel ciflow/all, ciflow/binaries, ciflow/binaries_wheel, ciflow/default, ciflow/trunk ✅ triggered
linux-bionic-py3.7-clang9 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/noarch, ciflow/trunk ✅ triggered
linux-bionic-rocm4.5-py3.7 ciflow/all, ciflow/default, ciflow/linux, ciflow/rocm, ciflow/trunk ✅ triggered
linux-docs ciflow/all, ciflow/cpu, ciflow/default, ciflow/docs, ciflow/linux, ciflow/trunk ✅ triggered
linux-vulkan-bionic-py3.7-clang9 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk, ciflow/vulkan ✅ triggered
linux-xenial-cuda11.3-py3.7-gcc7 ciflow/all, ciflow/cuda, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
linux-xenial-cuda11.3-py3.7-gcc7-bazel-test ciflow/all, ciflow/bazel, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
linux-xenial-py3-clang5-mobile-build ciflow/all, ciflow/default, ciflow/linux, ciflow/mobile, ciflow/trunk ✅ triggered
linux-xenial-py3-clang5-mobile-custom-build-static ciflow/all, ciflow/default, ciflow/linux, ciflow/mobile, ciflow/trunk ✅ triggered
linux-xenial-py3.7-clang7-asan ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/sanitizers, ciflow/trunk ✅ triggered
linux-xenial-py3.7-clang7-onnx ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/onnx, ciflow/trunk ✅ triggered
linux-xenial-py3.7-gcc5.4 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
linux-xenial-py3.7-gcc5.4-mobile-lightweight-dispatch-build ciflow/all, ciflow/cpu, ciflow/default, ciflow/libtorch, ciflow/linux, ciflow/mobile, ciflow/trunk ✅ triggered
linux-xenial-py3.7-gcc7 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
linux-xenial-py3.7-gcc7-no-ops ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
macos-arm64-binary-conda ciflow/binaries, ciflow/binaries_conda, ciflow/default ✅ triggered
macos-arm64-binary-wheel ciflow/binaries, ciflow/binaries_wheel, ciflow/default ✅ triggered
macos-binary-conda ciflow/binaries, ciflow/binaries_conda, ciflow/default ✅ triggered
macos-binary-libtorch-cxx11-abi ciflow/binaries, ciflow/binaries_libtorch, ciflow/default ✅ triggered
macos-binary-libtorch-pre-cxx11 ciflow/binaries, ciflow/binaries_libtorch, ciflow/default ✅ triggered
macos-binary-wheel ciflow/binaries, ciflow/binaries_wheel, ciflow/default ✅ triggered
pytorch-linux-xenial-py3-clang5-android-ndk-r19c-gradle-custom-build-single ciflow/all, ciflow/android, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
pytorch-linux-xenial-py3-clang5-android-ndk-r19c-gradle-custom-build-single-full-jit ciflow/all, ciflow/android, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/trunk ✅ triggered
win-vs2019-cpu-py3 ciflow/all, ciflow/cpu, ciflow/default, ciflow/trunk, ciflow/win ✅ triggered
win-vs2019-cuda11.3-py3 ciflow/all, ciflow/cuda, ciflow/default, ciflow/trunk, ciflow/win ✅ triggered
windows-binary-conda ciflow/binaries, ciflow/binaries_conda, ciflow/default ✅ triggered
windows-binary-libtorch-debug ciflow/all, ciflow/binaries, ciflow/binaries_libtorch, ciflow/default, ciflow/trunk ✅ triggered
windows-binary-libtorch-release ciflow/all, ciflow/binaries, ciflow/binaries_libtorch, ciflow/default, ciflow/trunk ✅ triggered
windows-binary-wheel ciflow/all, ciflow/binaries, ciflow/binaries_wheel, ciflow/default, ciflow/trunk ✅ triggered
Skipped Workflows
caffe2-linux-xenial-py3.7-gcc5.4 ciflow/all, ciflow/cpu, ciflow/linux, ciflow/trunk 🚫 skipped
docker-builds ciflow/all, ciflow/trunk 🚫 skipped
ios-12-5-1-arm64 ciflow/all, ciflow/ios, ciflow/macos, ciflow/scheduled 🚫 skipped
ios-12-5-1-arm64-coreml ciflow/all, ciflow/ios, ciflow/macos, ciflow/scheduled 🚫 skipped
ios-12-5-1-arm64-custom-ops ciflow/all, ciflow/ios, ciflow/macos, ciflow/scheduled 🚫 skipped
ios-12-5-1-arm64-metal ciflow/all, ciflow/ios, ciflow/macos, ciflow/scheduled 🚫 skipped
ios-12-5-1-x86-64 ciflow/all, ciflow/ios, ciflow/macos, ciflow/trunk 🚫 skipped
ios-12-5-1-x86-64-coreml ciflow/all, ciflow/ios, ciflow/macos, ciflow/trunk 🚫 skipped
libtorch-linux-xenial-cuda10.2-py3.7-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux, ciflow/trunk 🚫 skipped
libtorch-linux-xenial-cuda11.3-py3.7-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux, ciflow/trunk 🚫 skipped
linux-bionic-cuda10.2-py3.9-gcc7 ciflow/all, ciflow/cuda, ciflow/linux, ciflow/slow, ciflow/trunk 🚫 skipped
linux-docs-push ciflow/all, ciflow/cpu, ciflow/linux, ciflow/scheduled 🚫 skipped
linux-xenial-cuda11.3-py3.7-gcc7-no-ops ciflow/all, ciflow/cuda, ciflow/linux, ciflow/trunk 🚫 skipped
macos-10-15-py3-arm64 ciflow/all, ciflow/macos, ciflow/trunk 🚫 skipped
macos-10-15-py3-lite-interpreter-x86-64 ciflow/all, ciflow/macos, ciflow/trunk 🚫 skipped
macos-11-py3-x86-64 ciflow/all, ciflow/macos, ciflow/trunk 🚫 skipped
parallelnative-linux-xenial-py3.7-gcc5.4 ciflow/all, ciflow/cpu, ciflow/linux, ciflow/trunk 🚫 skipped
periodic-libtorch-linux-bionic-cuda11.5-py3.7-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux, ciflow/scheduled 🚫 skipped
periodic-linux-bionic-cuda11.5-py3.7-gcc7 ciflow/all, ciflow/cuda, ciflow/linux, ciflow/scheduled 🚫 skipped
periodic-linux-xenial-cuda10.2-py3-gcc7-slow-gradcheck ciflow/all, ciflow/cuda, ciflow/linux, ciflow/scheduled, ciflow/slow, ciflow/slow-gradcheck 🚫 skipped
periodic-linux-xenial-cuda11.3-py3.7-gcc7-debug ciflow/all, ciflow/cuda, ciflow/linux, ciflow/scheduled 🚫 skipped
periodic-win-vs2019-cuda11.5-py3 ciflow/all, ciflow/cuda, ciflow/scheduled, ciflow/win 🚫 skipped
pytorch-linux-xenial-py3-clang5-android-ndk-r19c-build ciflow/all, ciflow/android, ciflow/cpu, ciflow/linux, ciflow/trunk 🚫 skipped
pytorch-xla-linux-bionic-py3.7-clang8 ciflow/all, ciflow/cpu, ciflow/linux, ciflow/trunk, ciflow/xla 🚫 skipped

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Mar 9, 2022

🔗 Helpful links

💊 CI failures summary and remediations

As of commit c5b4d27 (more details on the Dr. CI page):


💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

…s in cudnn Conv.cpp to an utilities file"

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

[ghstack-poisoned]
…s in cudnn Conv.cpp to an utilities file"

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

[ghstack-poisoned]
@dzdang
Copy link
Contributor Author

dzdang commented Mar 19, 2022

@dzdang has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

…s in cudnn Conv.cpp to an utilities file"

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

Differential Revision: [D34995805](https://our.internmc.facebook.com/intern/diff/D34995805)

[ghstack-poisoned]
dzdang added a commit that referenced this pull request Mar 19, 2022
…Conv.cpp to an utilities file

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

ghstack-source-id: 755c1c2
Pull Request resolved: #73957
@dzdang
Copy link
Contributor Author

dzdang commented Mar 19, 2022

@dzdang has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@dzdang
Copy link
Contributor Author

dzdang commented Mar 21, 2022

@jerryzh168
I'm not sure if utils.h is set up in a good way here. As you can see, it contains the code for (1) the cudnn packed parameters and (2) auxiliary functions for conv & linear. Maybe it would be clearer if (1) and (2) were in separate files? The fbgemm & qnnpack utils files only contain packed parameters stuff, i think

…s in cudnn Conv.cpp to an utilities file"

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

Differential Revision: [D34995805](https://our.internmc.facebook.com/intern/diff/D34995805)

[ghstack-poisoned]
@dzdang
Copy link
Contributor Author

dzdang commented Mar 21, 2022

@dzdang has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

dzdang added 3 commits March 21, 2022 07:26
…s in cudnn Conv.cpp to an utilities file"

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

Differential Revision: [D34995805](https://our.internmc.facebook.com/intern/diff/D34995805)

[ghstack-poisoned]
…s in cudnn Conv.cpp to an utilities file"

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

Differential Revision: [D34995805](https://our.internmc.facebook.com/intern/diff/D34995805)

[ghstack-poisoned]
…s in cudnn Conv.cpp to an utilities file"

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

Differential Revision: [D34995805](https://our.internmc.facebook.com/intern/diff/D34995805)

[ghstack-poisoned]
…s in cudnn Conv.cpp to an utilities file"

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

Differential Revision: [D34995805](https://our.internmc.facebook.com/intern/diff/D34995805)

[ghstack-poisoned]
…s in cudnn Conv.cpp to an utilities file"

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

Differential Revision: [D34995805](https://our.internmc.facebook.com/intern/diff/D34995805)

[ghstack-poisoned]
@dzdang
Copy link
Contributor Author

dzdang commented Mar 23, 2022

@dzdang has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

…s in cudnn Conv.cpp to an utilities file"

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

Differential Revision: [D34995805](https://our.internmc.facebook.com/intern/diff/D34995805)

[ghstack-poisoned]
@dzdang
Copy link
Contributor Author

dzdang commented Mar 23, 2022

@dzdang has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

facebook-github-bot pushed a commit that referenced this pull request Mar 23, 2022
…Conv.cpp to an utilities file (#73957)

Summary:
Pull Request resolved: #73957

Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test Plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

Differential Revision:
D34995805
D34995805

Reviewed By: jerryzh168

Pulled By: dzdang

fbshipit-source-id: 15ea78af2927df583bf4adb596b255412186f902
@github-actions
Copy link
Contributor

Hey @dzdang.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

shahofblah pushed a commit that referenced this pull request Mar 25, 2022
…Conv.cpp to an utilities file (#73957)

Summary:
Pull Request resolved: #73957

Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test Plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

Differential Revision:
D34995805
D34995805

Reviewed By: jerryzh168

Pulled By: dzdang

fbshipit-source-id: 15ea78af2927df583bf4adb596b255412186f902
(cherry picked from commit 6a1260c)
NesrineMHB pushed a commit to NesrineMHB/pytorch that referenced this pull request Apr 8, 2022
…Conv.cpp to an utilities file

Summary:
Auxiliary functions in Conv.cpp that are applicable to a linear layer operator have been moved to
a utils.h file so that Conv.cpp and the future Linear.cpp file can both use it.

Test plan:
This file is simply a refactorization and should only affect the cudnn
conv operator. We can run the following unit test:
```
python test/test_quantization.py TestQuantizedConv.test_qconv2d_cudnn
```

ghstack-source-id: b498ac0
Pull Request resolved: pytorch/pytorch#73957
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants