[dpdk-dev] How kernel can share the mem from dpdk hugepage?

[Kyle Larose]

All of this information is in shared memory, is it not? For example,
you could patch the ring library to give a programmable interface to
the following function:
http://dpdk.org/doc/api/rte__ring_8h.html#a7bfcef0ad324fcc4c03bcb59cd7e867f.
This would allow you to see the full set of rings in a process that
has attached as a secondary to DPDK. Write a process that does this,
and then interfaces with whatever you have running in the kernel.

Ultimately, the architecture is pulling from userspace and pushing
into the kernel, rather than pulling directly from the kernel.

Does that help?

Thanks,

Kyle

On Thu, Oct 1, 2015 at 11:53 AM, 张伟 <zhangwqh at 126.com> wrote:
> Hi all,
>
>
> I want to ask does anybody know how kernel can share the info from dpdk hugepage. My project has a requirement which kernel needs to get some info from dpdk application. Eg, in multi-process example, every client has a shared ring buffer with server. The shared ring contains some meta data of packets. Is it possible that dpdk share this info to kernel, then kernel can access it? What are the key points that can help to achieve the goal?