From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 0BE322C65 for ; Tue, 8 Mar 2016 02:39:12 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP; 07 Mar 2016 17:39:11 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,554,1449561600"; d="scan'208";a="665521949" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by FMSMGA003.fm.intel.com with ESMTP; 07 Mar 2016 17:39:11 -0800 Received: from fmsmsx117.amr.corp.intel.com (10.18.116.17) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 7 Mar 2016 17:39:11 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by fmsmsx117.amr.corp.intel.com (10.18.116.17) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 7 Mar 2016 17:39:11 -0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.136]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.42]) with mapi id 14.03.0248.002; Tue, 8 Mar 2016 09:38:40 +0800 From: "Xie, Huawei" To: Stephen Hemminger Thread-Topic: [dpdk-dev] [PATCH v2 0/5] virtio: Tx performance improvements Thread-Index: AdFHkIEcLZU+WrxzTSqdZam/b6/SDg== Date: Tue, 8 Mar 2016 01:38:39 +0000 Message-ID: References: <1445231772-17467-1-git-send-email-stephen@networkplumber.org> <2330408.2AHZ8BdDek@xps13> <20160304101732.144d8901@xeon-e3> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v2 0/5] virtio: Tx performance improvements X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 01:39:13 -0000 On 3/5/2016 2:17 AM, Stephen Hemminger wrote:=0A= > Resending them now. I don't understand the issue with merge-able header.= =0A= > Virtio negotiation is symmetric, if receiver is using merge-able header= =0A= > then the transmitter needs to send it also.=0A= =0A= Yes, both receiver and transmitter use the same format of header though=0A= merge-able is actually only meaningful in RX path.=0A=