From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [ [PATCH v2] 01/13] virtio: Introduce config RTE_VIRTIO_INC_VECTOR Date: Fri, 18 Dec 2015 19:11:21 +0100 Message-ID: <2938160.ovecZPVEJY@xps13> References: <1450098032-21198-1-git-send-email-sshukla@mvista.com> <20151218093342.78fc5f72@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Stephen Hemminger Return-path: Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id 3594B5A86 for ; Fri, 18 Dec 2015 19:12:37 +0100 (CET) Received: by mail-wm0-f46.google.com with SMTP id l126so74919986wml.0 for ; Fri, 18 Dec 2015 10:12:37 -0800 (PST) In-Reply-To: <20151218093342.78fc5f72@xeon-e3> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2015-12-18 09:33, Stephen Hemminger: > On Fri, 18 Dec 2015 09:52:29 +0000 > "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 for TX. We also did some > > optimization for single segment and non-offload case in TX, without > > using SSE, which also gives ~60% performance improvement, in Qian's > > result. My optimization is mostly for single segment and non-offload > > case, which i calls simple rx/tx. > > I plan to add virtio/vhost performance benchmark so that we could easily > > measure the performance difference for each patch. > > > > Indirect and any layout features are useful for multiple segment > > transmitted packet mbufs. I had acked your patch at the first time, and > > thought it is applied. I don't understand why you say it is ignored by > > Intel. > > Sorry, did not mean to blame Intel, ... more that why didn't it get in 2.2? I've already answered to this question: http://dpdk.org/ml/archives/dev/2015-December/030540.html There was a compilation error and you have not followed up.