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

David Marchand david.marchand at redhat.com
Wed Oct 30 11:25:36 CET 2019


On Wed, Oct 30, 2019 at 11:17 AM Jakub Grajciar -X (jgrajcia -
PANTHEON TECH SRO at Cisco) <jgrajcia at cisco.com> wrote:
> > > On 8/22/2019 9:18 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).
> >
> > Do you really want this additional configuration in your driver or can't you
> > enable/disable the functional

Ah, I must have context-switched when writing this mail.. and forgot
to delete this part, sorry.
You can ignore.

>         Performance with multi file segments is worse than non-zero copy, so there is no reason to implement.


[snip]

> > I don't like the name of this API, since it gives the impression it returns
> > "segments"..
> > But on the other hand, this is aligned with the mcfg field: people touching the
> > internals have more chances to see there is an exported API.
>
>         Do you have any suggestions? How about rte_mcfg_get_single_file_segments_parameter()?

Nop, let's keep it as you proposed.
Thanks.


-- 
David Marchand



More information about the dev mailing list