* [dpdk-dev] DPDK secondary process access to mbufs using rte_pktmbuf_attach_extbuf()
@ 2020-12-04 13:07 Pranab Das
2020-12-07 18:58 ` Stephen Hemminger
0 siblings, 1 reply; 2+ messages in thread
From: Pranab Das @ 2020-12-04 13:07 UTC (permalink / raw)
To: dev
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-dev] DPDK secondary process access to mbufs using rte_pktmbuf_attach_extbuf()
2020-12-04 13:07 [dpdk-dev] DPDK secondary process access to mbufs using rte_pktmbuf_attach_extbuf() Pranab Das
@ 2020-12-07 18:58 ` Stephen Hemminger
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2020-12-07 18:58 UTC (permalink / raw)
To: Pranab Das; +Cc: dev
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-12-07 18:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-04 13:07 [dpdk-dev] DPDK secondary process access to mbufs using rte_pktmbuf_attach_extbuf() Pranab Das
2020-12-07 18:58 ` Stephen Hemminger
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).