On Fri, Dec 18, 2015 at 06:16:36PM +0530, Santosh Shukla wrote:
> On Fri, Dec 18, 2015 at 4:54 AM, Stephen Hemminger
> wrote:
> > On Thu, 17 Dec 2015 17:32:38 +0530
> > Santosh Shukla wrote:
> >
> >> On Mon, Dec 14, 2015 at 6:30 PM, Santosh Shukla
> >> wrote:
> >> > virtio_recv_pkts_vec and oth
2015-12-18 09:33, Stephen Hemminger:
> On Fri, 18 Dec 2015 09:52:29 +
> "Xie, Huawei" wrote:
> > > low level SSE bit twiddling.
> > Hi Stephen:
> > We only did SSE twiddling to RX, which almost doubles the performance
> > comparing to normal path in virtio/vhost performance test case. Indire
On Fri, Dec 18, 2015 at 4:54 AM, Stephen Hemminger
wrote:
> On Thu, 17 Dec 2015 17:32:38 +0530
> Santosh Shukla wrote:
>
>> On Mon, Dec 14, 2015 at 6:30 PM, Santosh Shukla
>> wrote:
>> > virtio_recv_pkts_vec and other virtio vector friend apis are written for
>> > sse/avx
>> > instructions. Fo
2015-12-18 09:52, Xie, Huawei:
> On 12/18/2015 7:25 AM, Stephen Hemminger wrote:
> > On Thu, 17 Dec 2015 17:32:38 +0530
> > Santosh Shukla wrote:
> >
> >> On Mon, Dec 14, 2015 at 6:30 PM, Santosh Shukla
> >> wrote:
> >>> virtio_recv_pkts_vec and other virtio vector friend apis are written for
>
On 12/18/2015 7:25 AM, Stephen Hemminger wrote:
> On Thu, 17 Dec 2015 17:32:38 +0530
> Santosh Shukla wrote:
>
>> On Mon, Dec 14, 2015 at 6:30 PM, Santosh Shukla
>> wrote:
>>> virtio_recv_pkts_vec and other virtio vector friend apis are written for
>>> sse/avx
>>> instructions. For arm64 in par
On Fri, 18 Dec 2015 09:52:29 +
"Xie, Huawei" wrote:
> > low level SSE bit twiddling.
> Hi Stephen:
> We only did SSE twiddling to RX, which almost doubles the performance
> comparing to normal path in virtio/vhost performance test case. Indirect
> and any layout feature enabling are mostly
On Thu, Dec 17, 2015 at 03:24:35PM -0800, Stephen Hemminger wrote:
> On Thu, 17 Dec 2015 17:32:38 +0530
> Santosh Shukla wrote:
>
> > On Mon, Dec 14, 2015 at 6:30 PM, Santosh Shukla
> > wrote:
> > > virtio_recv_pkts_vec and other virtio vector friend apis are written for
> > > sse/avx
> > > in
On Thu, Dec 17, 2015 at 5:33 PM, Thomas Monjalon
wrote:
> 2015-12-17 17:32, Santosh Shukla:
>> On Mon, Dec 14, 2015 at 6:30 PM, Santosh Shukla
>> wrote:
>> > virtio_recv_pkts_vec and other virtio vector friend apis are written for
>> > sse/avx
>> > instructions. For arm64 in particular, virtio
On Mon, Dec 14, 2015 at 6:30 PM, Santosh Shukla wrote:
> virtio_recv_pkts_vec and other virtio vector friend apis are written for
> sse/avx
> instructions. For arm64 in particular, virtio vector implementation does not
> exist(todo).
>
> So virtio pmd driver wont build for targets like i686, arm6
On Thu, 17 Dec 2015 17:32:38 +0530
Santosh Shukla wrote:
> On Mon, Dec 14, 2015 at 6:30 PM, Santosh Shukla wrote:
> > virtio_recv_pkts_vec and other virtio vector friend apis are written for
> > sse/avx
> > instructions. For arm64 in particular, virtio vector implementation does not
> > exist(t
2015-12-17 17:32, Santosh Shukla:
> On Mon, Dec 14, 2015 at 6:30 PM, Santosh Shukla wrote:
> > virtio_recv_pkts_vec and other virtio vector friend apis are written for
> > sse/avx
> > instructions. For arm64 in particular, virtio vector implementation does not
> > exist(todo).
> >
> > So virtio p
virtio_recv_pkts_vec and other virtio vector friend apis are written for sse/avx
instructions. For arm64 in particular, virtio vector implementation does not
exist(todo).
So virtio pmd driver wont build for targets like i686, arm64. By making
RTE_VIRTIO_INC_VECTOR=n, Driver can build for non-sse/
12 matches
Mail list logo
