From: David Marchand <david.marchand@redhat.com>
To: "Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco)"
<jgrajcia@cisco.com>
Cc: "Yigit, Ferruh" <ferruh.yigit@linux.intel.com>,
dev <dev@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5] net/memif: zero-copy slave
Date: Wed, 30 Oct 2019 11:25:36 +0100 [thread overview]
Message-ID: <CAJFAV8zchoLLLfg6NTsVW_m2rBBLVnK-CHFvy5GbcuGU7ixWaQ@mail.gmail.com> (raw)
In-Reply-To: <955be42a14bf484aae1afaf4157504f4@XCH-ALN-004.cisco.com>
On Wed, Oct 30, 2019 at 11:17 AM Jakub Grajciar -X (jgrajcia -
PANTHEON TECH SRO at Cisco) <jgrajcia@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
next prev parent reply other threads:[~2019-10-30 10:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 8:22 [dpdk-dev] [PATCH v4] " Jakub Grajciar
2019-07-10 15:06 ` Ferruh Yigit
2019-07-23 12:35 ` Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco)
2019-08-22 8:18 ` [dpdk-dev] [PATCH v5] " Jakub Grajciar
2019-10-04 13:23 ` Ferruh Yigit
2019-10-15 16:59 ` Ferruh Yigit
2019-10-17 11:52 ` Jakub Grajciar -X (jgrajcia - PANTHEON TECHNOLOGIES at Cisco)
2019-10-17 16:04 ` Ferruh Yigit
2019-10-17 16:45 ` Ferruh Yigit
2019-10-21 16:07 ` Ferruh Yigit
2019-10-25 16:44 ` Yigit, Ferruh
2019-10-29 14:28 ` David Marchand
2019-10-30 10:17 ` Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco)
2019-10-30 10:25 ` David Marchand [this message]
2019-11-04 11:03 ` [dpdk-dev] [PATCH v6] " Jakub Grajciar
2019-11-11 15:21 ` Ferruh Yigit
2019-11-11 15:24 ` Thomas Monjalon
2019-11-12 12:55 ` Jakub Grajciar -X (jgrajcia - PANTHEON TECH SRO at Cisco)
2019-11-11 15:49 ` David Marchand
2019-11-15 16:55 ` Ferruh Yigit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJFAV8zchoLLLfg6NTsVW_m2rBBLVnK-CHFvy5GbcuGU7ixWaQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@linux.intel.com \
--cc=jgrajcia@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).