From: Stephen Hemminger <stephen@networkplumber.org>
To: Pranab Das <pranab_das@affirmednetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK secondary process access to mbufs using rte_pktmbuf_attach_extbuf()
Date: Mon, 7 Dec 2020 10:58:27 -0800 [thread overview]
Message-ID: <20201207105827.31c0ded6@hermes.local> (raw)
In-Reply-To: <ff6cc212baf84ae58d71c25563fe69c5@affirmednetworks.com>
On Fri, 4 Dec 2020 13:07:01 +0000
Pranab Das <pranab_das@affirmednetworks.com> wrote:
> Hi
>
> I am wondering if the secondary DPDK processes can access the mbufs that are attached using rte_pktmbuf_attach_extbuf().
> The DPDK primary process allocates the buffer pool from the heap. Is there any example application that you can refer to ?
>
> Thank you very much
>
>
> * PKDas
When external buffers are used, they should come from memory that is visible and mapped
in both primary and secondary process (i.e hugepages). It is possible that a buggy
driver or application would not do that.
prev parent reply other threads:[~2020-12-07 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 13:07 Pranab Das
2020-12-07 18:58 ` Stephen Hemminger [this message]
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=20201207105827.31c0ded6@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=pranab_das@affirmednetworks.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).