From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] doc for multi-process communication
Date: Thu, 22 Feb 2018 02:44:12 +0000 [thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E365144A70D@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <7563007.pMa2n8IP3i@xps>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Thursday, February 15, 2018 8:17 PM
> To: Tan, Jianfeng
> Cc: dev@dpdk.org; Mcnamara, John; Ananyev, Konstantin; Burakov, Anatoly
> Subject: doc for multi-process communication
>
> Hi Jianfeng,
>
> The new experimental API for IPC is not documented a lot.
>
> We need some words in the prog guide, and some doxygen comments
> for the structures rte_mp_msg and rte_mp_reply.
>
> Please could you add this for the 18.05-rc1 release?
Yep, I'm on it. Thanks!
prev parent reply other threads:[~2018-02-22 2:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 12:17 Thomas Monjalon
2018-02-22 2:44 ` Tan, Jianfeng [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=ED26CBA2FAD1BF48A8719AEF02201E365144A70D@SHSMSX103.ccr.corp.intel.com \
--to=jianfeng.tan@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=thomas@monjalon.net \
/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).