From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] pdump: change to use generic multi-process channel
Date: Thu, 5 Apr 2018 19:17:20 +0800 [thread overview]
Message-ID: <06200725-4df7-74a0-42eb-7e19d30c5874@intel.com> (raw)
In-Reply-To: <3AEA2BF9852C6F48A459DA490692831F2A2C0302@irsmsx110.ger.corp.intel.com>
On 4/5/2018 6:37 PM, Pattan, Reshma wrote:
> Hi,
>
>> -----Original Message-----
>> From: Tan, Jianfeng
>> Sent: Wednesday, April 4, 2018 4:08 PM
>> To: dev@dpdk.org
>> Cc: Tan, Jianfeng <jianfeng.tan@intel.com>; Pattan, Reshma
>> <reshma.pattan@intel.com>
>> Subject: [PATCH v2] pdump: change to use generic multi-process channel
>>
>> The original code replies on the private channel for primary and secondary
>> communication. Change to use the generic multi-process channel.
>>
>> Note with this change, dpdk-pdump will be not compatible with old version
>> DPDK applications.
>>
>> Cc: reshma.pattan@intel.com
>>
>> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
>> ---
>> diff --git a/doc/guides/rel_notes/deprecation.rst
>> b/doc/guides/rel_notes/deprecation.rst
>> index 0c696f7..d55fd05 100644
>> --- a/doc/guides/rel_notes/deprecation.rst
>> +++ b/doc/guides/rel_notes/deprecation.rst
>> @@ -153,3 +153,7 @@ Deprecation Notices
>> be added between the producer and consumer structures. The size of the
>> structure and the offset of the fields will remain the same on
>> platforms with 64B cache line, but will change on other platforms.
>> +
>> +* pdump: As we changed to use generic IPC, ``rte_pdump_set_socket_dir``
>> +will be
>> + deprecated and removed in subsequent release; the parameter, path, of
>> + ``rte_pdump_init`` will also be removed.
> Do we need to mention about deprecation of below enums too?
> enum rte_pdump_socktype {
> RTE_PDUMP_SOCKET_SERVER = 1,
> RTE_PDUMP_SOCKET_CLIENT = 2
> };
Nice catch, will add in next version.
Thanks,
Jianfeng
>
> Thanks,
> Reshma
next prev parent reply other threads:[~2018-04-05 11:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 15:04 [dpdk-dev] [PATCH] " Jianfeng Tan
2018-03-20 16:37 ` Pattan, Reshma
2018-03-21 2:28 ` Tan, Jianfeng
2018-03-21 9:55 ` Pattan, Reshma
2018-03-27 1:26 ` Tan, Jianfeng
2018-03-27 8:21 ` Pattan, Reshma
2018-04-04 15:08 ` [dpdk-dev] [PATCH v2] " Jianfeng Tan
2018-04-05 9:45 ` Pattan, Reshma
2018-04-05 12:02 ` Tan, Jianfeng
2018-04-05 10:37 ` Pattan, Reshma
2018-04-05 11:17 ` Tan, Jianfeng [this message]
2018-04-05 11:54 ` [dpdk-dev] [PATCH v3] " Jianfeng Tan
2018-04-05 12:28 ` [dpdk-dev] [PATCH v4] " Jianfeng Tan
2018-04-05 12:35 ` Pattan, Reshma
2018-04-17 23:11 ` Thomas Monjalon
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=06200725-4df7-74a0-42eb-7e19d30c5874@intel.com \
--to=jianfeng.tan@intel.com \
--cc=dev@dpdk.org \
--cc=reshma.pattan@intel.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).