From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pallavi Kadam <pallavi.kadam@intel.com>
Subject: Re: [PATCH v8 08/10] eal: add minimum viable code for
 eal on windows
Date: Tue, 2 Apr 2019 14:21:53 -0700
Message-ID: <3ac129fb-709d-833a-234a-286793e2a322@intel.com>
References: <20190306041634.12976-1-anand.rawat@intel.com>
 <20190402035458.14664-1-anand.rawat@intel.com>
 <20190402035458.14664-9-anand.rawat@intel.com> <3868443.jK6Cv4ngdr@xps>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org, ranjit.menon@intel.com, jeffrey.b.shaw@intel.com,
 bruce.richardson@intel.com
To: Thomas Monjalon <thomas@monjalon.net>, Anand Rawat <anand.rawat@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24])
 by dpdk.org (Postfix) with ESMTP id 93B191B13A
 for <dev@dpdk.org>; Tue,  2 Apr 2019 23:21:55 +0200 (CEST)
In-Reply-To: <3868443.jK6Cv4ngdr@xps>
Content-Language: en-US
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>


On 4/2/2019 1:06 PM, Thomas Monjalon wrote:
> 02/04/2019 05:54, Anand Rawat:
>> Add windows specific logic for eal.c, eal_lcore.c,
>> eal_debug.c and eal_thread.c. Updated header files to
>> contain suitable function declaractions.
>>
>> Signed-off-by: Anand Rawat <anand.rawat@intel.com>
>> Signed-off-by: Pallavi Kadam <pallavi.kadam@intel.com>
>> Reviewed-by: Jeff Shaw <jeffrey.b.shaw@intel.com>
>> Reviewed-by: Ranjit Menon <ranjit.menon@intel.com>
>> ---
> [...]
>> +		/*
>> +		 * create communication pipes between master thread
>> +		 * and children
>> +		 */
>> +		if (_pipe(lcore_config[i].pipe_master2slave,
>> +			sizeof(char), _O_BINARY) < 0)
>> +			rte_panic("Cannot create pipe\n");
> rte_panic should be used only in applications, not in libraries.
> The application can do something in case of DPDK failure.
> Please remove all calls to rte_panic() during next weeks, thanks.

Ok, will try to incorporate in v9. Just curious, is this the major issue?

Calls to rte_panic() can be seen in linux/eal and freebsd/eal.

>
>