I replied to it the same day but unfortunately only to the author (see attached). My apologies.

Here's the answer:
"Depends on HW. If it can forward packets to different places then it can also be supported. But in most cases yes - for bifurcated drivers."


Regards,
Michael


-----Original Message-----
From: Thomas Monjalon <thomas@monjalon.net> 
Sent: Monday, 12 September 2022 16:33
To: Michael Savisko <michaelsav@nvidia.com>; Ori Kam <orika@nvidia.com>
Cc: andrew.rybchenko@oktetlabs.ru; dev@dpdk.org; Ferruh Yigit <ferruh.yigit@xilinx.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [RFC] ethdev: add send to kernel action

16/08/2022 11:50, Ferruh Yigit:
> On 8/11/2022 12:35 PM, Michael Savisko wrote:
> > CAUTION: This message has originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
> > 
> > 
> > In some cases application may receive a packet that should have been 
> > received by the kernel. In this case application uses KNI or other 
> > means to transfer the packet to the kernel.
> > This commit introduces rte flow action that the application may use 
> > to route the packet to the kernel while still in the HW.
> > 
> > Signed-off-by: Michael Savisko <michaelsav@nvidia.com>
> 
> I assume this only works for bifurcated drivers, right?

This question has not been replied after a month.
Please let's be more reactive.