This document introduces the usages and optimization strategies of non-linear operations in Concrete, focusing on comparisons, min/max operations, bitwise operations, and shifts. For a more in-depth explanation on advanced options, refer to the Table Lookup advanced documentation.
In Concrete, there are two types of operations:
Linear operations: These include additions, subtractions, and multiplications by an integer. They are computationally fast.
Non-linear operations: These require Table Lookups (TLUs) to maintain the semantic integrity of the user's program. The performance of TLUs is slower and vary depending on the bit width of the inputs.
Binary operations often require operands to have matching bit widths. This adjustment can be achieved in two ways: either directly within the MLIR or dynamically at execution time using a TLU. Each method has its own advantages and trade-offs, so Concrete provides multiple configuration options for non-linear functions.
MLIR adjustment: This method doesn't require an expensive TLU. However, it may affect other parts of your program if the adjusted operand is used elsewhere, potentially causing more changes.
Dynamic adjustment with TLU: This method is more localized and won’t impact other parts of your program, but it’s more expensive due to the cost of using a TLU.
In the following non-linear operations, we propose a certain number of configurations, using the two methods on the different operands. It’s not always clear which option will be the fastest, so we recommend trying out different configurations to see what works best for your circuit.
Note that you have the option to set show_mlir=True
to view how the MLIR handles TLUs and bit width changes. However, it's not essential to understand these details. So we recommend just testing the configurations and pick the one that performs best for your case.
For comparison, there are 7 available methods. Here's the general principle:
The config
can be one of the following:
fhe.ComparisonStrategy.CHUNKED
fhe.ComparisonStrategy.ONE_TLU_PROMOTED
fhe.ComparisonStrategy.THREE_TLU_CASTED
fhe.ComparisonStrategy.TWO_TLU_BIGGER_PROMOTED_SMALLER_CASTED
fhe.ComparisonStrategy.TWO_TLU_BIGGER_CASTED_SMALLER_PROMOTED
fhe.ComparisonStrategy.THREE_TLU_BIGGER_CLIPPED_SMALLER_CASTED
fhe.ComparisonStrategy.TWO_TLU_BIGGER_CLIPPED_SMALLER_PROMOTED
For min / max operations, there are 3 available methods. Here's the general principle:
The config
can be one of the following:
fhe.MinMaxStrategy.CHUNKED
(default)
fhe.MinMaxStrategy.ONE_TLU_PROMOTED
fhe.MinMaxStrategy.THREE_TLU_CASTED
For bit wise operations (typically, AND, OR, XOR), there are 5 available methods. Here's the general principle:
The config
can be one of the following:
fhe.BitwiseStrategy.CHUNKED
fhe.BitwiseStrategy.ONE_TLU_PROMOTED
fhe.BitwiseStrategy.THREE_TLU_CASTED
fhe.BitwiseStrategy.TWO_TLU_BIGGER_PROMOTED_SMALLER_CASTED
fhe.BitwiseStrategy.TWO_TLU_BIGGER_CASTED_SMALLER_PROMOTED
For shift operations, there are 2 available methods. Here's the general principle:
The shifts_with_promotion
is either True
or False
.
fhe.multivariate
All binary operations described in this document can also be implemented with the fhe.multivariate
function which is described in fhe.multivariate function documentation. Here's an example: