From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-00103a01.pphosted.com (mx0a-00103a01.pphosted.com [67.231.144.234]) by dpdk.org (Postfix) with ESMTP id D1A4E293C for ; Fri, 2 Sep 2016 17:54:40 +0200 (CEST) Received: from pps.filterd (m0000419.ppops.net [127.0.0.1]) by mx0a-00103a01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u82Frp59019937; Fri, 2 Sep 2016 11:54:39 -0400 Received: from mdwvexchht01.ciena.com (lin1-118-36-28.ciena.com [63.118.36.28]) by mx0a-00103a01.pphosted.com with ESMTP id 257932amrj-44 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Fri, 02 Sep 2016 11:54:38 -0400 Received: from MDWEXCHCGSIHT01.ciena.com (10.4.140.106) by MDWVEXCHHT01.ciena.com (10.4.156.175) with Microsoft SMTP Server (TLS) id 8.3.389.2; Fri, 2 Sep 2016 11:54:17 -0400 Received: from ONWVEXCHHT02.ciena.com (10.128.6.17) by MDWEXCHCGSIHT01.ciena.com (10.4.140.106) with Microsoft SMTP Server (TLS) id 8.3.389.2; Fri, 2 Sep 2016 11:54:16 -0400 Received: from ONWVEXCHMB04.ciena.com ([::1]) by ONWVEXCHHT02.ciena.com ([::1]) with mapi; Fri, 2 Sep 2016 11:54:16 -0400 From: "Mussar, Gary" To: Ferruh Yigit , "Wiles, Keith" CC: "dev@dpdk.org" Date: Fri, 2 Sep 2016 11:54:14 -0400 Thread-Topic: [dpdk-dev] rte_kni.ko with lo_mode=lo_mode_ring Thread-Index: AdIFKiSiSEU+xhyDRbamDo2VwIMlcQAB2ODQ Message-ID: References: <80a235de-226a-bcac-89f8-74550c0273ce@intel.com> In-Reply-To: <80a235de-226a-bcac-89f8-74550c0273ce@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-Product-Ver: SMEX-11.0.0.4179-8.000.1202-22552.000 X-TM-AS-Result: No--26.112000-8.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-09-02_05:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 impostorscore=0 lowpriorityscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1609020212 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 15:54:41 -0000 > -----Original Message----- > From: Ferruh Yigit [mailto:ferruh.yigit@intel.com] > Sent: Friday, September 02, 2016 10:55 AM > To: Wiles, Keith; Mussar, Gary > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] rte_kni.ko with lo_mode=3Dlo_mode_ring >=20 > On 9/2/2016 3:16 PM, Wiles, Keith wrote: > > HI Gary, > > > > Regards, > > Keith > > > >> On Sep 2, 2016, at 8:39 AM, Mussar, Gary wrote: > >> > >> 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 > understand this value. This wasn't an issue in the past since the kni cod= e would > simply disable lo_mode if you passed in an unknown value. > >> > >> The Ubuntu 4.4.0-36-generic kernel no longer loads the module if the p= assed > value is not in the table of known values (the 4.4.0-34-generic kernel wo= uld still > load the module). > >> > >> I have 2 questions: > >> 1) > >> Why does pktgen specify using a value for lo_mode that the source does= not > 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, = which > 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 maintains the= KNI > code. >=20 > "lo_mode_ring" is not supported loopback mode, supported ones are: > lo_mode_none > lo_mode_fifo > lo_mode_fifo_skb >=20 > Please point the document with incorrect usage. The files with the incorrect usage are: pktgen-dpdk/README.md pktgen-dpdk/setup.sh >=20 > > > >> > >> 2) > >> Is the Ubuntu kernel being over aggressive in parameter checking or is= this a > "good" thing? If it is good, then should the pktgen docs be indicating th= at an > unsupported value be used for lo_mode? > > > > I assume the Ubuntu Kernel is attempting to protect itself. Each time t= he > kernel is updated it is a good think to recompile DPDK and the KNI kernel= module > or the module may not load because of a version mis-match. >=20 > Yes this looks like the issue, > instead of kernel version or parameter protection, kernel-module version > mismatch. Please re-compile kni module. Recompiling the kni module makes it happier. Thanks. >=20 > > > >> > >> Gary > > >=20