From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0054.outbound.protection.outlook.com [157.56.111.54]) by dpdk.org (Postfix) with ESMTP id F3A4E9AA9 for ; Tue, 17 Mar 2015 15:57:37 +0100 (CET) Received: from BLUPR03MB1460.namprd03.prod.outlook.com (25.163.81.157) by BLUPR03MB246.namprd03.prod.outlook.com (10.255.213.18) with Microsoft SMTP Server (TLS) id 15.1.118.15; Tue, 17 Mar 2015 14:57:36 +0000 Received: from BN3PR0301MB1202.namprd03.prod.outlook.com (25.161.207.155) by BLUPR03MB1460.namprd03.prod.outlook.com (25.163.81.157) with Microsoft SMTP Server (TLS) id 15.1.99.14; Tue, 17 Mar 2015 14:57:35 +0000 Received: from BN3PR0301MB1202.namprd03.prod.outlook.com ([25.161.207.155]) by BN3PR0301MB1202.namprd03.prod.outlook.com ([25.161.207.155]) with mapi id 15.01.0112.000; Tue, 17 Mar 2015 14:57:35 +0000 From: "Dey, Souvik" To: "dev@dpdk.org" Thread-Topic: Bug in rte_kni Thread-Index: AdBgwkzPPWK2wniGTdWaXeHpU7tpHQ== Date: Tue, 17 Mar 2015 14:57:34 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [121.242.142.135] authentication-results: dpdk.org; dkim=none (message not signed) header.d=none; x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB1460; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB246; x-microsoft-antispam-prvs: x-forefront-antispam-report: BMV:0; SFV:NSPM; SFS:(10009020)(6009001)(53754006)(76576001)(40100003)(19625215002)(122556002)(62966003)(450100001)(2656002)(19580395003)(87936001)(92566002)(46102003)(2351001)(66066001)(229853001)(2900100001)(102836002)(15975445007)(16236675004)(2501003)(77156002)(110136001)(19300405004)(86362001)(54356999)(99286002)(50986999)(33656002)(74316001); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR03MB1460; H:BN3PR0301MB1202.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5001010); SRVR:BLUPR03MB1460; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB1460; x-forefront-prvs: 0518EEFB48 MIME-Version: 1.0 X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Mar 2015 14:57:34.9758 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 29a671dc-ed7e-4a54-b1e5-8da1eb495dc3 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB1460 X-OriginatorOrg: sonusnet.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "Dutta, Biswanath" Subject: [dpdk-dev] Bug in rte_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: Tue, 17 Mar 2015 14:57:38 -0000 Hi All, I was trying out handling of jumbo packets in DPDK, but I c= ame across an issue where I see that the multiple segmented mbufs are not s= upported in the rte_kni and due to which the packets are not properly handl= ed/converted to skb before giving it to the kernel. Is there any specific r= eason of not supporting multi-segment packet in kni ? -- Regards, Souvik