Skip to content

Select CUDA v2 bounds checking for Triton TBE (#4484) - #4484

Closed
stashuk-olek wants to merge 1 commit into
meta-pytorch:mainfrom
stashuk-olek:export-D114279989
Closed

Select CUDA v2 bounds checking for Triton TBE (#4484)#4484
stashuk-olek wants to merge 1 commit into
meta-pytorch:mainfrom
stashuk-olek:export-D114279989

Conversation

@stashuk-olek

@stashuk-olek stashuk-olek commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Summary:

Use BoundsCheckMode.V2 for Triton TBE standalone index validation. This preserves the existing warning and offset-repair behavior while reducing validation overhead before Triton forward.

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Aug 5, 2026
@meta-codesync

meta-codesync Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@stashuk-olek has exported this pull request. If you are a Meta employee, you can view the originating Diff in D114279989.

stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
@meta-codesync meta-codesync Bot changed the title Select CUDA v2 bounds checking for Triton TBE Select CUDA v2 bounds checking for Triton TBE (#4484) Aug 5, 2026
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 5, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 6, 2026
Summary:

Cuda wasn't using bounds check, but triton did. Match the both to make it fair comparison

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
@meta-codesync meta-codesync Bot changed the title Select CUDA v2 bounds checking for Triton TBE (#4484) Select CUDA v2 bounds checking for Triton TBE Aug 7, 2026
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 8, 2026
Summary:

Use BoundsCheckMode.V2 for Triton TBE standalone index validation. This preserves the existing warning and offset-repair behavior while reducing validation overhead before Triton forward.

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 8, 2026
Summary:

Use BoundsCheckMode.V2 for Triton TBE standalone index validation. This preserves the existing warning and offset-repair behavior while reducing validation overhead before Triton forward.

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
Summary:

Use BoundsCheckMode.V2 for Triton TBE standalone index validation. This preserves the existing warning and offset-repair behavior while reducing validation overhead before Triton forward.

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 8, 2026
Summary:

Use BoundsCheckMode.V2 for Triton TBE standalone index validation. This preserves the existing warning and offset-repair behavior while reducing validation overhead before Triton forward.

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 8, 2026
Summary:

Use BoundsCheckMode.V2 for Triton TBE standalone index validation. This preserves the existing warning and offset-repair behavior while reducing validation overhead before Triton forward.

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 8, 2026
Summary:

Use BoundsCheckMode.V2 for Triton TBE standalone index validation. This preserves the existing warning and offset-repair behavior while reducing validation overhead before Triton forward.

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
@meta-codesync meta-codesync Bot changed the title Select CUDA v2 bounds checking for Triton TBE Select CUDA v2 bounds checking for Triton TBE (#4484) Aug 8, 2026
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 8, 2026
Summary:

Use BoundsCheckMode.V2 for Triton TBE standalone index validation. This preserves the existing warning and offset-repair behavior while reducing validation overhead before Triton forward.

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 8, 2026
Summary:

Use BoundsCheckMode.V2 for Triton TBE standalone index validation. This preserves the existing warning and offset-repair behavior while reducing validation overhead before Triton forward.

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
stashuk-olek added a commit to stashuk-olek/torchrec that referenced this pull request Aug 8, 2026
Summary:

Use BoundsCheckMode.V2 for Triton TBE standalone index validation. This preserves the existing warning and offset-repair behavior while reducing validation overhead before Triton forward.

Reviewed By: axeisghost, TroyGarden

Differential Revision: D114279989
@meta-codesync meta-codesync Bot closed this in c95e01a Aug 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant