[dpdk-dev] [PATCH v6] net/memif: zero-copy slave

Ferruh Yigit ferruh.yigit at intel.com
Fri Nov 15 17:55:39 CET 2019


On 11/11/2019 3:49 PM, David Marchand wrote:
> On Mon, Nov 11, 2019 at 4:21 PM Ferruh Yigit <ferruh.yigit at intel.com> wrote:
>>
>> On 11/4/2019 11:03 AM, Jakub Grajciar wrote:
>>> Zero-copy slave support for memif PMD.
>>> Slave interface exposes DPDK memory to
>>> master interface. Only single file segments
>>> are supported (EAL option --single-file-segments).
>>>
>>> Signed-off-by: Jakub Grajciar <jgrajcia at cisco.com>
>>> ---
>>>  doc/guides/nics/memif.rst                     |  42 +-
>>>  drivers/net/memif/Makefile                    |   1 +
>>>  drivers/net/memif/memif_socket.c              |  65 +--
>>>  drivers/net/memif/meson.build                 |   1 +
>>>  drivers/net/memif/rte_eth_memif.c             | 449 +++++++++++++++++-
>>>  drivers/net/memif/rte_eth_memif.h             |  11 +-
>>>  lib/librte_eal/common/eal_common_mcfg.c       |   7 +
>>>  .../common/include/rte_eal_memconfig.h        |  13 +
>>>  lib/librte_eal/rte_eal_version.map            |   1 +
>>>  9 files changed, 516 insertions(+), 74 deletions(-)
>>
>> net/memif part looks good to me,
>>
>> @David, @Anatoly, any concern on new eal API, is it good to go?
> 
> I am okay with exposing such an info from the mem config since it was
> exposed before.
> It will be experimental anyway.
> 

Reviewed-by: Ferruh Yigit <ferruh.yigit at intel.com>

Applied to dpdk-next-net/master, thanks.


More information about the dev mailing list