On 1 Jan 2026, at 16:25, Eli Britstein via dev wrote:
> On 02/12/2025 16:04, Eelco Chaudron wrote:
>> The dpif-netdev implementation currently invokes offload flow APIs
>> indirectly through the netdev-offload layer. These calls are tightly
>> coupled to dpif-netdev logic, but the long-term goal is to have all
>> offload handling centralized in the dpif-offload-dpdk implementation.
>>
>> To progress toward that goal, we begin by decoupling hardware offload
>> logic from dpif-netdev and transitioning it into dpif-offload-dpdk.
>> As a preparatory step, we replace indirect netdev offload calls with
>> direct calls. This allows us to clean up the existing netdev-offload
>> code more easily and isolate remaining dependencies.
> Can we avoid the "temporary" functions that will be refactored later and have
> more "complete" commits?
Yes, we could do that. The reason for not doing so yet is to keep the behavior
unchanged while gradually removing the netdev-offload layer. Doing this in one
step would result in a very large and hard-to-review change set.
These intermediate steps also make it much easier to run unit tests and
validate each stage without breaking anything.
Given that we are only four days away from the code-complete deadline,
introducing larger refactors that do not affect the final outcome of this
series does not seem worthwhile at this point.
>> This patch does not complete the transition but sets the foundation for
>> a cleaner separation between the datapath interface and offload
>> infrastructure.
>>
>> Signed-off-by: Eelco Chaudron <[email protected]>
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
