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
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
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)
> >
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
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 to rx return points.
_mm_storeu_si128((__m128i *)&rx_pkts[pos+2], mbp2
5 matches
Mail list logo