On 2020-03-23 23:19, Jerin Jacob wrote:
On Mon, Mar 23, 2020 at 11:11 PM dwilder wrote:
Thanks you for your review Jerin. See my responses are inline.
On 2020-03-20 06:24, Jerin Jacob wrote:
> On Fri, Feb 21, 2020 at 4:22 AM David Wilder
> wrote:
>>
>> If --no-huge is set
On 2020-03-23 23:19, Jerin Jacob wrote:
On Mon, Mar 23, 2020 at 11:11 PM dwilder wrote:
Thanks you for your review Jerin. See my responses are inline.
On 2020-03-20 06:24, Jerin Jacob wrote:
> On Fri, Feb 21, 2020 at 4:22 AM David Wilder
> wrote:
>>
>> If --no-huge is set
Thanks you for your review Jerin. See my responses are inline.
On 2020-03-20 06:24, Jerin Jacob wrote:
On Fri, Feb 21, 2020 at 4:22 AM David Wilder
wrote:
If --no-huge is set and iova-mode has not been specified force VA
mode.
If --no-huge and --iova-mode=PA is requested error out as this
On 2020-03-13 01:16, Ruifeng Wang wrote:
For environments (such as containers) where hugetlbfs are not
available,
some unit tests can be run with 'no-huge' option.
fast-tests suites is generated dynamically according to hugetlbfs
availability in building environment. This allows unit test to ru
On 2020-03-16 13:47, David Christensen wrote:
The include file rte_debug.h is pulled into x86 builds through the
following callchain:
lib/librte_eal/common/include/generic/rte_cycles.h:17,
lib/librte_eal/common/include/arch/x86/rte_cycles.h:13,
lib/librte_eal/common/include/arch/x86/rte_spinlock
On 2020-02-19 11:41, David Marchand wrote:
Let's prune the jobs list to limit the amount of time spent by the
robot
in Travis.
Since meson enables automatically the relevant components, there is not
much gain in testing with extra_packages vs required_packages only.
For a given arch/compiler/e
On 2020-02-19 05:46, David Marchand wrote:
On Wed, Feb 19, 2020 at 2:10 AM David Wilder
wrote:
This change follows the example of aarch64 Travis support
by adding support for ppc64le gcc builds. Limitations for
ppc64le are the same as aarch64 as described in commit
31bb45bcfd.
checkpatch di
On 2020-02-13 14:17, Thomas Monjalon wrote:
13/02/2020 21:58, dwilder:
On 2020-02-13 12:32, Thomas Monjalon wrote:
> 13/02/2020 21:24, David Wilder:
>> - The --no-huge option requires iova-mode=VA.
>> On ppc64le iova-mode defaults to PA therefor
>> VA mode must be expli
On 2020-02-13 12:32, Thomas Monjalon wrote:
13/02/2020 21:24, David Wilder:
- The --no-huge option requires iova-mode=VA.
On ppc64le iova-mode defaults to PA therefor
VA mode must be explicitly set.
Should we make VA mode automatic when using --no-huge?
Should we log an error message when
On 2019-12-20 01:37, Ruifeng Wang wrote:
Add Travis compilation jobs for aarch64. gcc/clang compilations for
static/shared libraries are added.
Some limitations for current aarch64 Travis support:
1. Container is used. Huge page is not available due to security
reason.
2. Missing kernel header
On 2019-06-04 14:04, Thomas Monjalon wrote:
04/06/2019 22:25, dwilder:
On 2019-06-03 15:30, Thomas Monjalon wrote:
> 27/05/2019 11:41, Bruce Richardson:
>> On Fri, May 24, 2019 at 09:04:04AM -0700, David Wilder wrote:
>> > Setting RTE_MAX_LCORE to reflect the largest avail
On 2019-06-03 15:30, Thomas Monjalon wrote:
27/05/2019 11:41, Bruce Richardson:
On Fri, May 24, 2019 at 09:04:04AM -0700, David Wilder wrote:
> Setting RTE_MAX_LCORE to reflect the largest available configuration.
> Adding defines for missing RTE_MACHINE_CPUFLAGs.
>
> Signed-off-by: David Wilder
Hi Kevin-
I tested 8.11.2 RC1 on IBM Power9 hardware. No issues or performance
degradation were observed.
Tests run:
* Single port stability test using l3fwd (16 cpus) and TRex, tested 64
and 1500 byte packets at a 0.0% drop rate for 4 hours each.
System tested:
- IBM Power9 Model 8335-1
You may share some release validation results
by replying to this message (at dev@dpdk.org).
If no objection, the version 19.05.0 will be out on May 13.
Hi Thomas-
I tested 19.05-rc4 on IBM Power9 hardware. No issues were were seen.
Tests run:
* Single port stability test using l3fwd (16
Hi-
The following describes the test completed for 19.05-rc3 run on IBM
Power9 hardware:
* Single port stability test using l3fwd (16 cpus) and TRex, tested 64
and 1500 byte packets at a 0.0% drop rate for 4 hours each.
No errors or regressions were seen.
System tested:
- IBM Power9 Mode
Hi-
The following describes the tests that we ran on top of the 19.05 branch
on IBM Power9 hardware.
* Single port stability test using l3fwd (16 cpus) and TRex, tested 64
and 1500 byte packets at a 0.0% drop rate for 4 hours each.
No errors or regressions were seen.
System tested:
- IBM P
I am seeing a build break when building on ubuntu 19.04 beta after this
commit (cbb66daa3).
The build produces a number of the following errors.
drivers/net/mlx5/mlx5_glue.c:194:2: error: implicit declaration of
function ‘free’
drivers/net/mlx5/mlx5_glue.c:552:11: error: incompatible imp
On 2018-11-15 07:11, Burakov, Anatoly wrote:
On 14-Nov-18 8:40 PM, David Wilder wrote:
Please include this patch in 18.11 as well, this patch is not suitable
for 17.11.
Small note: while this patch is not suitable for 17.11 as is, it can
be made suitable if you drop the memalloc part. I copied
On 2018-11-07 08:00, Thomas Monjalon wrote:
The AltiVec header file breaks boolean type:
error: incompatible types when initializing type
'__vector _bool int' {aka '_vector(4) __bool int'} using type 'int'
If __APPLE_ALTIVEC__ is defined, then bool type is redefined
and conflicts with stdbool.h
On 2018-11-07 02:03, Thomas Monjalon wrote:
05/11/2018 22:20, Pradeep Satyanarayana:
From: Thomas Monjalon
> 30/08/2018 13:58, Christian Ehrhardt:
> > On Thu, Aug 30, 2018 Takeshi T Yoshimura wrote:
> > > Hi,
> > > I could reproduce the issue you reported in 18.08 with my ppc64le
> > > box wit
Hi Christian
I am new to the list thus was unable to reply directly to your post:
[PATCH v2] ppc64: fix compilation of when AltiVec is enabled
I reproduce the build error on my ppc64le box and verified that your V2
patch corrects the build failure on both RHEL 7.5 and Ubuntu 18.04.
Thanks fo
21 matches
Mail list logo
