You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following script using thunder.jit is supposed to run layer norm backward using the innerOuter scheduler in nvFuser. But the generated fusion is rejected with msg: # Scheduler _inner_outer_persistent_ ***rejected*** because : unsupported post reduction normalization
Further check found the msg comes from SchedulerTopologyChecker::hasNonNormalizePostReductionBCast
Found unresolved broadcast after reduction: T31_l[ iS60{2048}, bS61{1 ex 8192} ] -> T40_l[ iS78{2048}, iS107{i1} ]
T40_l[ iS78{2048}, iS107{i1} ]
= T31_l[ iS60{2048}, bS61{1 ex 8192} ]
+ T39_l[ iS76{2048}, iS106{i1} ];
T31 has a post reduction broadcast dim bS61. The check wants to ensure bS61 is same to the extent of the reduction dim by checking it is mapped with a dim goes to reduction. The related fusion ir is:
It uses the backward dep chain 40 -> 31 -> 30 -> 29 -> 28 -> 27 ,and the mapped IDs are {iS107{i1}, bS61, bS61, bS57, bS55, bS53}. At T27 --> T25, no id is mapped any more and the chain breaks!
The text was updated successfully, but these errors were encountered:
The following script using thunder.jit is supposed to run layer norm backward using the innerOuter scheduler in nvFuser. But the generated fusion is rejected with msg:
# Scheduler _inner_outer_persistent_ ***rejected*** because : unsupported post reduction normalization
Further check found the msg comes from
SchedulerTopologyChecker::hasNonNormalizePostReductionBCast
T31
has a post reduction broadcast dimbS61
. The check wants to ensurebS61
is same to the extent of the reduction dim by checking it is mapped with a dim goes to reduction. The related fusion ir is:It uses the backward dep chain
40 -> 31 -> 30 -> 29 -> 28 -> 27
,and the mapped IDs are {iS107{i1}, bS61, bS61, bS57, bS55, bS53}. AtT27 --> T25
, no id is mapped any more and the chain breaks!The text was updated successfully, but these errors were encountered: