"Richardson, Bruce" writes:
>> -Original Message-
>> From: Thomas Monjalon [mailto:thomas.monja...@6wind.com]
>> Sent: Thursday, March 9, 2017 9:26 AM
>> To: Richardson, Bruce
>> Cc: Aaron Conole ; dev@dpdk.org; Stephen Hemminger
>>
>>
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monja...@6wind.com]
> Sent: Thursday, March 9, 2017 9:26 AM
> To: Richardson, Bruce
> Cc: Aaron Conole ; dev@dpdk.org; Stephen Hemminger
>
> Subject: Re: [dpdk-dev] [PATCH v6 00/26] linux/eal: Remove most
2017-03-09 09:11, Bruce Richardson:
> On Wed, Mar 08, 2017 at 10:58:27PM +0100, Thomas Monjalon wrote:
> > Hi,
> >
> > Thanks for the work.
> > I think it needs to be completed to have the same behaviour on bsdapp.
>
> Ideally, yes, but I also don't think the lack of BSD changes should
> block th
On Wed, Mar 08, 2017 at 10:58:27PM +0100, Thomas Monjalon wrote:
> Hi,
>
> Thanks for the work.
> I think it needs to be completed to have the same behaviour on bsdapp.
Ideally, yes, but I also don't think the lack of BSD changes should
block the inclusion of this set. In terms of application wri
Hi,
Thanks for the work.
I think it needs to be completed to have the same behaviour on bsdapp.
As a another version is required, I add some small comments about
the formatting.
I think you should use the form "do not panic on " for most
of the commits.
Some commits may be squashed (see below):
From: Aaron Conole
In many cases, it's enough to simply let the application know that the
call to initialize DPDK has failed. A complete halt can then be
decided by the application based on error returned (and the app could
even attempt a possible re-attempt after some corrective action by the
u
6 matches
Mail list logo
