Interface function: In inference scenarios, this operator performs the preprocessing computation for Multi-Head Latent Attention. The main computation process consists of five paths.
- After multiplying the input with for downsampling and RmsNorm, the first path multiplies the result with and , followed by two upsampling operations to obtain , while the second path multiplies the result with and applies rotary position encoding (ROPE) to obtain .
- The third path multiplies the input with for downsampling and RmsNorm, and then passes the result into the cache to obtain .
- The fourth path multiplies the input with , applies rotary position encoding (ROPE), and then stores the result into another cache to obtain .
- The fifth path processes the output through DynamicQuant to generate quantization parameters.
- The weight parameters
[object Object],[object Object], and[object Object]are required to be provided in NZ format.
Formula:
RmsNorm formula
The computation formula of the query, including downsampling, RmsNorm, and two upsampling operations.
Performs rotary position encoding (ROPE) to the query.
The computation formula of the key, including downsampling and RmsNorm. The computation result is stored in the cache.
Performs rotary position encoding (ROPE) to the key and stores the result in the cache.
Dequant Scale Query Nope calculation formula:
Each operator has calls. First, [object Object] is called to obtain the input parameters and compute the required workspace size based on the process. Then, [object Object] is called to perform computation.
Parameters
[object Object]undefined
Returns
[object Object]: status code. For details, see .[object Object]The first-phase API performs input parameter validation. The following errors may be returned:
[object Object]undefined
Deterministic computation:
[object Object]defaults to deterministic implementation.
Shape field description
[object Object]undefined
When transposing is not performed, the dimensions of
[object Object],[object Object], and[object Object]are represented as[object Object].Shape restrictions:
- When BS fusion is used for
[object Object], that is ,[object Object]- The shape of
[object Object]and[object Object]is[object Object]. - The shape of
[object Object]is[object Object]. - The shape of
[object Object]is[object Object]. - The shape of
[object Object]is[object Object]. - The shape of
[object Object]is[object Object]. - In the full quantization scenario, the shape of
[object Object]is[object Object]. In other scenarios, the shape is[object Object].
- The shape of
- When BS fusion is not used for
[object Object], that is ,[object Object]- The shape of
[object Object]and[object Object]is[object Object]. - The shape of
[object Object]is[object Object]. - The shape of
[object Object]is[object Object]. - The shape of
[object Object]is[object Object]. - The shape of
[object Object]is[object Object]. - In the full quantization scenario, the shape of
[object Object]is[object Object]. In other scenarios, the shape is[object Object].
- The shape of
- One or more of the B, S, T, and Skv values can be 0. That is, input parameters related to the shape and B, S, T, and Skv values can be empty tensors. Other input parameters do not support empty tensors.
- If the values of B, S, and T are 0,
[object Object]and[object Object]output empty tensors, and[object Object]and[object Object]are not updated. - If the value of Skv is 0,
[object Object],[object Object], and[object Object]are calculated normally, and[object Object]and[object Object]are not updated. That is, an empty tensor is output.
- If the values of B, S, and T are 0,
- When BS fusion is used for
The
[object Object][object Object]API supports the following scenarios:In different quantization scenarios, the combination of dtype and shape of parameters must meet the following conditions:
[object Object]
The following example is for reference only. For details, see .