From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [67.231.154.164]) by dpdk.org (Postfix) with ESMTP id 6EAAD23C for ; Wed, 18 Jul 2018 17:20:50 +0200 (CEST) X-Virus-Scanned: Proofpoint Essentials engine Received: from webmail.solarflare.com (uk.solarflare.com [193.34.186.16]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1-us3.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id 37DDA9C0097; Wed, 18 Jul 2018 15:20:49 +0000 (UTC) Received: from [192.168.1.16] (85.187.13.33) by ukex01.SolarFlarecom.com (10.17.10.4) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Wed, 18 Jul 2018 16:20:33 +0100 To: "Burakov, Anatoly" CC: "dev@dpdk.org" , Sergio Gonzalez Monroy From: Andrew Rybchenko Message-ID: <8bc76811-ac29-d7f2-e4c3-12b50fd44dba@solarflare.com> Date: Wed, 18 Jul 2018 18:20:26 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Originating-IP: [85.187.13.33] X-ClientProxiedBy: ocex03.SolarFlarecom.com (10.20.40.36) To ukex01.SolarFlarecom.com (10.17.10.4) X-TM-AS-Product-Ver: SMEX-11.0.0.1191-8.100.1062-23976.003 X-TM-AS-Result: No--4.400200-0.000000-31 X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No X-MDID: 1531927249-uyZzxnB6m9nf Subject: [dpdk-dev] Memory allocated using rte_zmalloc() has non-zeros 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: Wed, 18 Jul 2018 15:20:50 -0000 Hi Anatoly, I'm investigating issue which finally comes to the fact that memory allocated using rte_zmalloc() has non zeros. If I add memset just after allocation, everything is perfect and works fine. I've found out that memset was removed from rte_zmalloc_socket() some time ago: >>> commit b78c9175118f7d61022ddc5c62ce54a1bd73cea5 Author: Sergio Gonzalez Monroy Date:   Tue Jul 5 12:01:16 2016 +0100     mem: do not zero out memory on zmalloc     Zeroing out memory on rte_zmalloc_socket is not required anymore since all     allocated memory is already zeroed.     Signed-off-by: Sergio Gonzalez Monroy <<< but may be something has changed now that made above statement false. I observe the problem when memory is reallocated. I.e. I configure 7 queues, start, stop, reconfigure to 3 queues, start. Memory is allocated on start and freed on stop, since we have less queues on the second start it is allocated in a different way and reuses previously allocated/freed memory. Do you have any ideas what could be wrong? Andrew.