From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eomereadig@gmail.com>
Received: from mail-ob0-f175.google.com (mail-ob0-f175.google.com
 [209.85.214.175]) by dpdk.org (Postfix) with ESMTP id 668D18D99
 for <dev@dpdk.org>; Fri,  2 Oct 2015 15:09:44 +0200 (CEST)
Received: by obcgx8 with SMTP id gx8so81132727obc.3
 for <dev@dpdk.org>; Fri, 02 Oct 2015 06:09:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type:content-transfer-encoding;
 bh=z5gSwxzON5iyRn3egtJ0t4LZRWC6SyJ7W+bYe6OmI7Y=;
 b=DPYbgH8nWXg1XZEysh/LTHgdCy6kFn2Oo6KVnDRxKTB3nNLB0cz/ea+IL01nAwDUJt
 OZoWZz4E4TWA0q9lzVT96nIlY7l2ZD3ZZDZbvc8KKdz7BaGoXnKXSzsNtBHdkObZizUM
 7BxP7QkPhldCUxYMrd1uA2mIxE/L+hp12/E1aUuQ4pG6ymA7aIKM2G8AIxXupxPIMU4i
 CR74UuMazma/HjNIEyfo3r4b2L3CXaxymTVJrX3N5iDDZ6ghwHtwJrJBfwUmSnXy7/Gv
 9gQSJUBOkVZ7ZDAgP5NDWA4xgLD+kMkrbLU2lgqeEFOem4qnMz208d+anzh6thRar5xP
 1eJA==
MIME-Version: 1.0
X-Received: by 10.182.16.135 with SMTP id g7mr9128256obd.67.1443791383903;
 Fri, 02 Oct 2015 06:09:43 -0700 (PDT)
Received: by 10.76.168.197 with HTTP; Fri, 2 Oct 2015 06:09:43 -0700 (PDT)
In-Reply-To: <a61428d.3d5d.150241c131d.Coremail.zhangwqh@126.com>
References: <a61428d.3d5d.150241c131d.Coremail.zhangwqh@126.com>
Date: Fri, 2 Oct 2015 09:09:43 -0400
Message-ID: <CAMFWN9mcVXxrVk_LesyoaCoWKdqo-yh-SKGb-kxFhfyt1VXpMw@mail.gmail.com>
From: Kyle Larose <eomereadig@gmail.com>
To: =?UTF-8?B?5byg5Lyf?= <zhangwqh@126.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] How kernel can share the mem from dpdk hugepage?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2015 13:09:44 -0000

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, =E5=BC=A0=E4=BC=9F <zhangwqh@126.com> wrot=
e:
> Hi all,
>
>
> I want to ask does anybody know how kernel can share the info from dpdk h=
ugepage. My project has a requirement which kernel needs to get some info f=
rom dpdk application. Eg, in multi-process example, every client has a shar=
ed ring buffer with server. The shared ring contains some meta data of pack=
ets. Is it possible that dpdk share this info to kernel, then kernel can ac=
cess it? What are the key points that can help to achieve the goal?