DPDK patches and discussions
 help / color / mirror / Atom feed
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 20:02:43 +0800	[thread overview]
Message-ID: <4edca215-ab68-0a98-6953-ad729731bba0@intel.com> (raw)
In-Reply-To: <3AEA2BF9852C6F48A459DA490692831F2A2C023A@irsmsx110.ger.corp.intel.com>

Sorry, it seems that I missed this email.


On 4/5/2018 5:45 PM, Pattan, Reshma wrote:
> Hi
>
>> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
>> ---
>> Note this patch needs this patch set:
>> http://dpdk.org/dev/patchwork/patch/36814/
>> v2:
>>    - Update doc for deprecation of API, rte_pdump_set_socket_dir,
>>      and API change for rte_pdump_init.
>>    - Add notice for known incompatibility issue in doc.
>>   app/pdump/main.c                       |   6 +-
>>   doc/guides/rel_notes/deprecation.rst   |   4 +
>>   doc/guides/rel_notes/release_18_05.rst |   7 +
>>   lib/librte_pdump/Makefile              |   3 +-
>>   lib/librte_pdump/rte_pdump.c           | 423 +++++----------------------------
>>   lib/librte_pdump/rte_pdump.h           |   1 +
>>   6 files changed, 84 insertions(+), 360 deletions(-)
>> diff --git a/lib/librte_pdump/rte_pdump.c b/lib/librte_pdump/rte_pdump.c
>> +
>>
>
>> +
>> +	/* recv client requests */
>> +	if (mp_msg->len_param != sizeof(*cli_req)) {
>> +		RTE_LOG(ERR, PDUMP, "failed to recv from client\n");
>> +		resp->err_value = EINVAL;
> 	resp->err_value = -EINVAL

OK, this keeps consistent with other places in this file.

>
>> -	/* save the socket in local configuration */
>> -	pdump_socket_fd = socket_fd;
>> +	snprintf(mp_resp.name, RTE_MP_MAX_NAME_LEN, PDUMP_MP);
>> +	mp_resp.len_param = sizeof(*resp);
>> +	mp_resp.num_fds = 0;
>> +	if (rte_mp_reply(&mp_resp, peer) < 0)
>> +		RTE_LOG(ERR, PDUMP, "failed to send to client:%s, %s:%d\n",
>> +			strerror(rte_errno), __func__, __LINE__);
>>
> If failed to send the reply should'nt we return -1?

Yes, will fix it.

>
>>   	return 0;
>>   }
>>
>>   int
>> -rte_pdump_set_socket_dir(const char *path, enum rte_pdump_socktype
>> type)
>> +rte_pdump_set_socket_dir(const char *path __rte_unused,
>> +			 enum rte_pdump_socktype type __rte_unused)
>>   {
> What about enum rte_pdump_socktype in header file? When to delete them?

Will deprecate it.

>
> We need to update doxygen comments in header file for rte_pdump_init and rte_pdump_uninit()? What do you say.

I'll try to find a flag for deprecating a param. If you know how to do 
that, please let me know.

Thanks,
Jianfeng

>
> Thanks,
> Reshma

  reply	other threads:[~2018-04-05 12:02 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 [this message]
2018-04-05 10:37   ` Pattan, Reshma
2018-04-05 11:17     ` Tan, Jianfeng
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=4edca215-ab68-0a98-6953-ad729731bba0@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).