Skip to content

Conversation

@larryliu0820
Copy link
Contributor

Summary: In lightweight dispatch, we only need to register root ops. Unlike in the dispatcher world, the transitive closure of the operators doesn't need to go through dispatcher or op registry.

Test Plan: Rely on unit tests

Differential Revision: D35104401

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Mar 24, 2022

🔗 Helpful links

💊 CI failures summary and remediations

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


  • 1/2 failures introduced in this PR
  • 1/2 broken upstream at merge base 7f996b8 on Mar 24 from 12:09pm to 6:13pm

1 failure not recognized by patterns:

Job Step Action
GitHub Actions pull / linux-docs / build-docs (python) Unknown 🔁 rerun

🚧 1 fixed upstream failure:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

If your commit is older than viable/strict, run these commands:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

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.

@facebook-github-bot facebook-github-bot added oncall: jit Add this issue/PR to JIT oncall triage queue fb-exported labels Mar 24, 2022
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D35104401

1 similar comment
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D35104401

…ch (pytorch#74664)

Summary:
This change adds the following logic:

If lightweight dispatch is enabled, do not generate `TORCH_LIBARAY` API calls for operator schema and implementations, since these operators will be registered into JIT op registry.

`skip_dispatcher_op_registration` is an existing argument to `gen.py`. With that set, `RegisterDispatchKey.cpp` will not generate `m.def` and `m.impl` for each native function. This logic will be removed once we find a better way to skip op registration into dispatcher.

Pull Request resolved: pytorch#74664

Test Plan: Rely on unit tests for lightweight dispatch.

Reviewed By: priyaramani

Differential Revision: D34634300

Pulled By: larryliu0820

fbshipit-source-id: 2882b96b30c8e6edadb6efa065c6310747cc08dc
Summary:
Pull Request resolved: pytorch#74663

In lightweight dispatch, we only need to register root ops. Unlike in the dispatcher world, the transitive closure of the operators doesn't need to go through dispatcher or op registry.

Test Plan: Rely on unit tests

Reviewed By: priyaramani

Differential Revision: D35104401

fbshipit-source-id: c5e9d64b866d92135a11cad2f10adb63701edda7
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D35104401

facebook-github-bot pushed a commit that referenced this pull request Mar 25, 2022
Summary:
Pull Request resolved: #74663

In lightweight dispatch, we only need to register root ops. Unlike in the dispatcher world, the transitive closure of the operators doesn't need to go through dispatcher or op registry.

Test Plan: Rely on unit tests

Reviewed By: priyaramani

Differential Revision: D35104401

fbshipit-source-id: 1a2df571880ac3c8625985c01bd89a2bb9566af9
@github-actions
Copy link
Contributor

Hey @larryliu0820.
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.

@larryliu0820 larryliu0820 linked an issue Mar 25, 2022 that may be closed by this pull request
@larryliu0820 larryliu0820 added the topic: new features topic category label Mar 25, 2022
shahofblah pushed a commit that referenced this pull request Mar 25, 2022
Summary:
Pull Request resolved: #74663

In lightweight dispatch, we only need to register root ops. Unlike in the dispatcher world, the transitive closure of the operators doesn't need to go through dispatcher or op registry.

Test Plan: Rely on unit tests

Reviewed By: priyaramani

Differential Revision: D35104401

fbshipit-source-id: 1a2df571880ac3c8625985c01bd89a2bb9566af9
(cherry picked from commit 16207fa)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla signed fb-exported oncall: jit Add this issue/PR to JIT oncall triage queue topic: new features topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[PyTorch] Lightweight dispatch

2 participants