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 16626156 for ; Wed, 25 Dec 2013 01:49:07 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 24 Dec 2013 16:46:23 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.95,546,1384329600"; d="scan'208";a="457335355" Received: from fmsmsx107.amr.corp.intel.com ([10.19.9.54]) by orsmga002.jf.intel.com with ESMTP; 24 Dec 2013 16:50:15 -0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX107.amr.corp.intel.com (10.19.9.54) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 24 Dec 2013 16:50:14 -0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.186]) by SHSMSX151.ccr.corp.intel.com ([10.239.6.50]) with mapi id 14.03.0123.003; Wed, 25 Dec 2013 08:50:12 +0800 From: "Zhang, Helin" To: Daniel Kaminsky Thread-Topic: [dpdk-dev] Loop back mode of the KNI Thread-Index: AQHO/NiBXz+hGdABjUC9ipqOKW+QCZpkHBPw Date: Wed, 25 Dec 2013 00:50:11 +0000 Message-ID: References: In-Reply-To: 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] Loop back mode of the KNI 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: Wed, 25 Dec 2013 00:49:08 -0000 Hi Daniel Thanks for your good catch! Yes. That's a bug, and it will be fixed in later DPDK releases. Regards, Helin -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Daniel Kaminsky Sent: Friday, December 20, 2013 12:36 AM To: dev@dpdk.org Subject: [dpdk-dev] Loop back mode of the KNI Hi all, We're working on the KNI and we see a strange behavior which seems like a b= ug in the the kernel module. When running with *lo_mode=3Dlo_mode_fifo *everything works as expected, th= e packets looks similar on the ingress and egress. But when running with *lo_mode=3Dlo_mode_fifo_skb *the packets on the egres= s doesn't include the first 14 bytes (the ethernet header) although the pac= kets size doesn't change. Thanks, Daniel