Re: [dpdk-dev] [PATCH 0/3 v2] disable vector PMD for i686

2017-04-28 Thread Ferruh Yigit
On 4/28/2017 10:26 AM, Bruce Richardson wrote: > On Fri, Apr 28, 2017 at 11:14:24AM +0200, Thomas Monjalon wrote: >> 27/04/2017 11:25, Bruce Richardson: >>> On Thu, Apr 27, 2017 at 03:01:04AM -0400, Qi Zhang wrote: Vector PMD is not designed for i686 orginally, but it still can be active

Re: [dpdk-dev] [PATCH 0/3 v2] disable vector PMD for i686

2017-04-28 Thread Bruce Richardson
On Fri, Apr 28, 2017 at 11:14:24AM +0200, Thomas Monjalon wrote: > 27/04/2017 11:25, Bruce Richardson: > > On Thu, Apr 27, 2017 at 03:01:04AM -0400, Qi Zhang wrote: > > > Vector PMD is not designed for i686 orginally, but it still can be active > > > with i686 compile option. > > > Below are observ

Re: [dpdk-dev] [PATCH 0/3 v2] disable vector PMD for i686

2017-04-28 Thread Thomas Monjalon
27/04/2017 11:25, Bruce Richardson: > On Thu, Apr 27, 2017 at 03:01:04AM -0400, Qi Zhang wrote: > > Vector PMD is not designed for i686 orginally, but it still can be active > > with i686 compile option. > > Below are observed failure when vPMD is invovled on i686 > > (but may not limited to) > >

Re: [dpdk-dev] [PATCH 0/3 v2] disable vector PMD for i686

2017-04-27 Thread Bruce Richardson
On Thu, Apr 27, 2017 at 03:01:04AM -0400, Qi Zhang wrote: > Vector PMD is not designed for i686 orginally, but it still can be active > with i686 compile option. > Below are observed failure when vPMD is invovled on i686 > (but may not limited to) > > 1) memory overwrite when assign 2 mbuf points