From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id CE28F3F9 for ; Fri, 2 Sep 2016 16:16:04 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP; 02 Sep 2016 07:16:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,271,1470726000"; d="scan'208";a="756542111" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by FMSMGA003.fm.intel.com with ESMTP; 02 Sep 2016 07:16:03 -0700 Received: from fmsmsx102.amr.corp.intel.com (10.18.124.200) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 2 Sep 2016 07:16:02 -0700 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.149]) by FMSMSX102.amr.corp.intel.com ([10.18.124.200]) with mapi id 14.03.0248.002; Fri, 2 Sep 2016 07:16:02 -0700 From: "Wiles, Keith" To: "Mussar, Gary" CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev]rte_kni.ko with lo_mode=lo_mode_ring Thread-Index: AQHSBSSItGjc2vhwtUWhOwO2LnWyfQ== Date: Fri, 2 Sep 2016 14:16:01 +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.255.83.221] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] rte_kni.ko with lo_mode=lo_mode_ring 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: Fri, 02 Sep 2016 14:16:05 -0000 HI Gary, Regards, Keith > On Sep 2, 2016, at 8:39 AM, Mussar, Gary wrote: >=20 > The pktgen docs state that the rte_kni.ko should be loaded with lo_mode= =3Dlo_mode_ring however the source in dpdk master does not appear to unders= tand this value. This wasn't an issue in the past since the kni code would = simply disable lo_mode if you passed in an unknown value. >=20 > The Ubuntu 4.4.0-36-generic kernel no longer loads the module if the pass= ed value is not in the table of known values (the 4.4.0-34-generic kernel w= ould still load the module). >=20 > I have 2 questions: > 1) > Why does pktgen specify using a value for lo_mode that the source does no= t support? Is lo_mode_ring something that is coming but not yet submitted? The KNI support and kernel module is more of a DPDK issue then Pktgen, whic= h is the application on top of DPDK. I do not know the reason lo_mode_ring = is not working correctly. Look in the Maintainers file and see who maintain= s the KNI code. >=20 > 2) > Is the Ubuntu kernel being over aggressive in parameter checking or is th= is a "good" thing? If it is good, then should the pktgen docs be indicating= that an unsupported value be used for lo_mode? I assume the Ubuntu Kernel is attempting to protect itself. Each time the k= ernel is updated it is a good think to recompile DPDK and the KNI kernel mo= dule or the module may not load because of a version mis-match. >=20 > Gary