From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from usmailout4.samsung.com (mailout4.w2.samsung.com [211.189.100.14]) by dpdk.org (Postfix) with ESMTP id 3FB762BA1 for ; Thu, 10 Aug 2017 13:19:19 +0200 (CEST) Received: from uscas1p1.samsung.com (unknown [182.198.245.206]) by usmailout4.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0OUG00LB6VG63J00@usmailout4.samsung.com> for dev@dpdk.org; Thu, 10 Aug 2017 07:19:18 -0400 (EDT) Received: from ussmges1.samsung.com (u109.gpu85.samsung.co.kr [203.254.195.109]) by uscas1p1.samsung.com (KnoxPortal) with ESMTP id 20170810111917uscas1p1a131159a7888360dc74490c458acaf7f~ZeA8fD8IP0777207772uscas1p1q; Thu, 10 Aug 2017 11:19:17 +0000 (GMT) Received: from uscas1p1.samsung.com ( [182.198.245.206]) by ussmges1.samsung.com (USCPEMTA) with SMTP id 73.3C.08231.4314C895; Thu, 10 Aug 2017 07:19:16 -0400 (EDT) Received: from uscpsbgex1.samsung.com (u122.gpu85.samsung.co.kr [203.254.195.122]) by uscas1p2.samsung.com (KnoxPortal) with ESMTP id 20170810111916uscas1p23d59a1410ec0ab85fd838aa241cba11f~ZeA7o83fP2093820938uscas1p2e; Thu, 10 Aug 2017 11:19:16 +0000 (GMT) X-AuditID: cbfec36d-f79cd6d000002027-a6-598c41342afe Received: from usmmp2.samsung.com ( [203.254.195.78]) by uscpsbgex1.samsung.com (USCPEXMTA) with SMTP id 8B.76.08403.3314C895; Thu, 10 Aug 2017 07:19:16 -0400 (EDT) Received: from SSI-EX2.ssi.samsung.com ([105.128.134.172]) by usmmp2.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0OUG00AY0VG3TQ40@usmmp2.samsung.com>; Thu, 10 Aug 2017 07:19:15 -0400 (EDT) Received: from SSI-EX2.ssi.samsung.com (105.128.2.227) by SSI-EX2.ssi.samsung.com (105.128.2.227) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.669.32; Thu, 10 Aug 2017 04:19:15 -0700 Received: from SSI-EX2.ssi.samsung.com ([fe80::2149:7df2:31b5:d9a0]) by SSI-EX2.ssi.samsung.com ([fe80::2149:7df2:31b5:d9a0%3]) with mapi id 15.01.0669.032; Thu, 10 Aug 2017 04:19:15 -0700 From: "Rohit Saini (Stellus)" To: 'Sergio Gonzalez Monroy' , "'dev@dpdk.org'" Thread-topic: [dpdk-dev] Use rte_malloc in application Thread-index: AQHTDDKWXd/XN24430GJENNNvZvTGqJ9fGEg Date: Thu, 10 Aug 2017 11:19:15 +0000 Message-id: <3eec78a1002f41d4a7ccc9bb1d2f5ef2@stellus.com> In-reply-to: <2f989384-b5e8-f975-9a65-de5b4e3c0dd1@intel.com> Accept-Language: en-US Content-language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Originating-IP: [105.128.2.176] Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable MIME-version: 1.0 X-CFilter-Loop: Reflected X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLIsWRmVeSWpSXmKPExsWy7djXc7omjj2RBss3WVq8+7SdyWLFhCOM DkwevxYsZfVYvOclUwBTFJdNSmpOZllqkb5dAlfGnGezGAsO8Fa0fNVrYPzM1cXIySEhYCLR ffwJI4QtJnHh3nq2LkYuDiGBZYwSz1d+YAJJCAm0MUm8eJAI03D/9Q9miKIVjBLvphxggyj6 zyjR+LQMIvGRUeLqvz+sEM4BRonORaeZQarYBMwlrt54CdYhIpAksWzWGpYuRg4OYQFTiR1d ERBhM4kNt94wgoRFBIwkuo6ogIRZBFQlDi07BnYQr4CVxMurK8EmcgrYSqyccQ/MZgT64Pup NWA1zALiEs2tN1kgjhaUWDR7DzPMl/92PWSDsBUlnrecZISo15E4e2wdlK0t8eTdBVaIXYIS Pybfg5ojKXFwxQ0WkLckBA6xSzSfncIMcqeEgKzEpgNQ810kDi5ugKoXlnh1fAt7FyM7kC0j 8UgOYjqfxN9fjxgnMKrMQnLoLCRHzEJyxCwkRyxgZFnFKFJaXJybnlpsqFecmFtcmpeul5yf u4kRmChO/zucu4Nx9u6AQ4wCHIxKPLwcwt2RQqyJZcWVuYcYJTiYlUR4bxj1RArxpiRWVqUW 5ccXleakFh9ilOZgURLnrZshFCkkkJ5YkpqdmlqQWgSTZeLglGpglNYz2bX87y13+yOiIf1K L3a5cHvVMm4X4dnE6f54z8XS53ddxCbUxhZoOF+cwWZmr8xoyH+l/OHZzTJXRZfq1xx33bD9 0vKXWS9OnX1zu7VXLsMhxnvGEZfp68Oaosp3v3G5NtnVNmbZXoGD+W9Z709tPLxGeumaaSwp B+LN9TdMN/23K2WylxJLcUaioRZzUXEiAD1v+p4QAwAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGIsWRmVeSWpSXmKPExsVy+t9hP10Tx55IgwvdTBbvPm1nslgx4Qij A5PHrwVLWT0W73nJFMAU5WaTkZqYklqkkJqXnJ+SmZduqxQa4qZroaSQl5ibaqsUoesbEqSk UJaYUwrkGRmgAQfnAPdgJX27BLeMOc9mMRYc4K1o+arXwPiZq4uRk0NCwETi/usfzBC2mMSF e+vZuhi5OIQEljFKXD43gwXCaWSS2D/pDyOE85FR4seBuVCZA4wSsw7cZwfpZxMwl7h64yUb iC0ikCTRun0PUxcjB4ewgKnEjq4IiLCZxIZbbxhBwiICRhJdR1RAwiwCqhKHlh1jArF5Bawk Xl5dyQwx/gujxM6tX8ASnAK2Eitn3AM7lRHo1O+n1oDFmQXEJZpbb7JAvCAgsWTPeah3RCVe Pv7HCmErSjxvOckIUa8lsX7ncahebYkn7y6wQiwWlPgx+R7UHEmJgytusEwA+g7JillI2mch aZ+FpH0BI8sqRpHS4uLc9IpiQ73ixNzi0rx0veT83E2MkDiv2sF456vNIUYBDkYlHt4E0e5I IdbEsuLK3EOMEhzMSiK8N4x6IoV4UxIrq1KL8uOLSnNSiw8xmgJDaSKzlGhyPjAF5ZXEG5qY G5iaGBpZmhqamSqJ8/qsXxYuJJCeWJKanZpakFoE08fEwSnVwOi1vVvzFFuhhm5o+ufVvXO0 bs7+ar3nk5PD3N9t7LL1M9kue5z/Fv7h7Byr77Zh3MXqPKsUOg46NJ6esvbZ/E2Xrv7y2N/z 4H2ka/Rpf96vL9sUzUw/yxfbfHh+zjHWybtLuf6tX/YSn5mbrnh5z3a2Fd2t80cjINz/VKnE htQ8m4WLI8SLpJVYijMSDbWYi4oTAS1ZgQcJAwAA X-MTR: 20000000000000000@CPGS X-CMS-MailID: 20170810111916uscas1p23d59a1410ec0ab85fd838aa241cba11f X-Msg-Generator: CA X-Sender-IP: 203.254.195.122 CMS-TYPE: 301P X-HopCount: 7 X-CMS-RootMailID: 20170803055747uscas1p15fd0c2a998cf260734f89cc48192a61c X-RootMTR: 20170803055747uscas1p15fd0c2a998cf260734f89cc48192a61c References: <3d5197fb36ef4901907d785621f01da5@stellus.com> <2f989384-b5e8-f975-9a65-de5b4e3c0dd1@intel.com> Subject: Re: [dpdk-dev] Use rte_malloc in application X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2017 11:19:19 -0000 Thanks Sergio. It helped. There was a mistake the way I was linking dpdk wi= th my application. Thanks, Rohit -----Original Message----- From: Sergio Gonzalez Monroy [mailto:sergio.gonzalez.monroy@intel.com]=20 Sent: Thursday, August 03, 2017 1:59 PM To: Rohit Saini (Stellus) ; 'dev@dpdk.org' Subject: Re: [dpdk-dev] Use rte_malloc in application On 03/08/2017 07:12, Rohit Saini (Stellus) wrote: > With below code, I am getting this warning. > > warning: cast to pointer from integer of different size=20 > [-Wint-to-pointer-cast] > > my_node_t *data_ptr =3D (my_node_t *) rte_malloc(NULL,=20 > sizeof(my_node_t), 0); As far as I can see, the syntax looks correct. How are you building/linking your application? I would suggest to modify the DPDK examples/helloworld application to just = do a simple rte_malloc as a first step. Thanks, Sergio > Thanks, > Rohit > > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Rohit Saini=20 > (Stellus) > Sent: Thursday, August 03, 2017 11:28 AM > To: 'dev@dpdk.org' > Subject: [dpdk-dev] Use rte_malloc in application > > Hi, > I have a use case in my application where I need to implement my own memo= ry manager, rather than doing malloc/free everytime to kernel. > Instead of writing my own memory manager, I am thinking to use dpdk rte_m= alloc or rte_mempool. Please let me know if this is a good idea. > > Also, > > my_node_t *data_ptr =3D (my_node_t *) (uintptr_t) rte_malloc(NULL,=20 > sizeof(my_node_t), 0); > > data_ptr is pointing to some invalid memory. Am I doing anything wrong h= ere? > > > Thanks, > Rohit