sh} SSKrSSKJr SSKJrJr SSKrSSKJr SSKJ r J r SSK J r SSK Jr S/rSSS.S \R S \\ S \\\\\\44S \\S \R 4 Sjjjrg)Nfnmatch)OptionalUnion)_mesh_resources DeviceMesh)_validate_tp_mesh_dim) ParallelStyleparallelize_module src_data_rankmodule device_meshparallelize_planr returnc ^ [RRS5 U=(d [R"5n[ U5 Uc[ R"S5 U$[U[5(aX2l URX5$[U[5(aUR5HupEURS5n[U5S:Xa [!S5eU(dM9UR#S5m [%U 4SjUR'55nUH8upU(a SR)U5n [+U UX0US9 M,[+U UUUS9 M: U(aMvM U$[-S[/U5S 35e) a, Apply Tensor Parallelism in PyTorch by parallelizing modules or sub-modules based on a user-specified plan. We parallelize module or sub_modules based on a parallelize_plan. The parallelize_plan contains :class:`ParallelStyle`, which indicates how user wants the module or sub_module to be parallelized. User can also specify different parallel style per module fully qualified name (FQN). Note that ``parallelize_module`` only accepts a 1-D :class:`DeviceMesh`, if you have a 2-D or N-D :class:`DeviceMesh`, slice the DeviceMesh to a 1-D sub DeviceMesh first then pass to this API(i.e. ``device_mesh["tp"]``) Args: module (:class:`nn.Module`): Module to be parallelized. device_mesh (:class:`DeviceMesh`, optional): Object which describes the mesh topology of devices for the DTensor. If not specified, the call must be under a DeviceMesh context. parallelize_plan (Union[:class:`ParallelStyle`, Dict[str, :class:`ParallelStyle`]], optional): The plan used to parallelize the module. It can be either a :class:`ParallelStyle` object which contains how we prepare input/output for Tensor Parallelism or it can be a dict of module FQN and its corresponding :class:`ParallelStyle` object. If not specified, the call will do nothing at the moment. Keyword args: src_data_rank (int, optional): the rank of the source data for the logical/global tensor, it is used by :meth:`distribute_tensor` to scatter/broadcast the shards/replicas to other ranks. By default, we use ``group_rank=0`` on each DeviceMesh dimension as the source data to preserve the single-device semantic. If passing ``None`` explicitly, :meth:`parallelize_module` simply uses its local data instead of trying to preserve the single-device semantic via scatter/broadcast. Default: 0 Return: A :class:`nn.Module` object parallelized. Example:: >>> # xdoctest: +SKIP("distributed") >>> from torch.distributed.tensor.parallel import parallelize_module, ColwiseParallel >>> from torch.distributed.device_mesh import init_device_mesh >>> >>> # Define the module. >>> m = Model(...) >>> tp_mesh = init_device_mesh("cuda", (8,)) >>> m = parallelize_module(m, tp_mesh, {"w1": ColwiseParallel(), "w2": RowwiseParallel()}) >>> .. note:: For complex module architecture like Attention, MLP layers, we recommend composing different ParallelStyles together (i.e. ``ColwiseParallel`` and ``RowwiseParallel``) and pass as a parallelize_plan, to achieves the desired sharding computation. z4torch.distributed.tensor.parallel.parallelize_modulezNo parallelize_plan is provided and auto-parallel is not supported at the moment, so this parallelize_module call will do nothing..rz9Expect module path to be non-empty, but got empty string!c">[UST5$)Nrr)tatoms y/Users/tiagomarins/Projetos/claudeai/copy_bank/venv/lib/python3.13/site-packages/torch/distributed/tensor/parallel/api.py$parallelize_module..dsgadD1r zLExpect Union[ParallelStyle, Dict[str, ParallelStyle]] for parallelize_plan, z found!)torch_C_log_api_usage_oncerget_current_meshr warningswarn isinstancer r _applydictitemssplitlen ValueErrorpopfilternamed_childrenjoinr TypeErrortype) rrrr module_pathparallelize_style path_splitsmatched_children_ submodule leaf_pathrs @rr r sn HH  !WXC!A!A!CK+&  N  "M22)6&&&v;; $d + +.>.D.D.F *K%++C0K;1$ O+"q)#)1))+$ %5LA"$'HH'% +%'&:*7 +%'-*7 %5+ /GD  ""&'7"8!9 B  r)NN)rrtypingrrrtorch.nnnntorch.distributed.device_meshrr(torch.distributed.tensor.parallel._utilsr 'torch.distributed.tensor.parallel.styler __all__Moduler#strintr rrr@s" EJA  )-QUq $% q IIq *%q u]Dm9K4L%LMNq C= q YY q r