From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5F36C425DF for ; Mon, 18 Sep 2023 20:49:56 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 24AF94027E; Mon, 18 Sep 2023 20:49:56 +0200 (CEST) Received: from mail-pl1-f175.google.com (mail-pl1-f175.google.com [209.85.214.175]) by mails.dpdk.org (Postfix) with ESMTP id 1B0FE40275 for ; Mon, 18 Sep 2023 20:49:55 +0200 (CEST) Received: by mail-pl1-f175.google.com with SMTP id d9443c01a7336-1c39f2b4f5aso34853345ad.0 for ; Mon, 18 Sep 2023 11:49:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1695062994; x=1695667794; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=oqgYtSIzwEdstkJ6THrkYuAK8MlsKeFsCqcvT5S2AtY=; b=Sj0pdXD7sj34vFFhR78qMJ7jFkyjy+94+9pWgVSYG/bgbdbxXj5b5cMSw0h/tpNSa8 M+tZ7LqDdwKnpVF3u9sLbbKe4Pd3RB7x67NuwQoORlb9BLiv6gjfTNp5Tp4iPs/pusgx t8l+E6J+/IeRh3KJOovwyQThS0SUc7aMmtZ4YZHWQbprK2FlxzuXe+a3DL6FNbz9Quni iJNkmYM7NJfs7017CMksXcCmEXEsevZUnhLIsi7lFmvUIrMjaGOCE6/j9ND38YV5QGAx 0bv0mgwHlRfxovhzYdRGUikn//fQwS9VbjpbLgH551TMROAVrlrsDE8XptsIEZlGnQJN 4lWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695062994; x=1695667794; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=oqgYtSIzwEdstkJ6THrkYuAK8MlsKeFsCqcvT5S2AtY=; b=j0WfhI3wRL+ZtAbok0Lnn5oRwIvW+AtfwYxH6ePIp8+Tk9xpXlM49ayTVjTFLoYrLe mhXbJ9wvITbUh4mLTuiK0iw9QE4ADti0YO7RBxLDGdzpmmCLNLkBK5J/UCgz/K0QNm/i p9d/CFf37mhrNUCJKmSTig0Srr5ls7lRE2yVJSEZEr6mdtfw9D5QsyQx5s6zKsigK985 iY+OoS/i1RhcIaOsEKH0uViNN6JR4zQCMOO+DXW5swGvRzu099/WwxbjlpqEd/RMqDAW yY14teMM/LhvzkzpUggTqI8eg0tAx1SQ3a/CYdVrpbCAP5C/IHRR5PPDPag7/wVJP3oB gW/w== X-Gm-Message-State: AOJu0YxZEazFk72/f0GUIkehuj29RmBcmigz26A130o2AND5VsRVYNHX rAaw215xsymEq0Prjn8VkijM31TV202aSD1niW7j6g== X-Google-Smtp-Source: AGHT+IFzMQXtHWnDJVZ6XzCJCKPOz2Dx7dU6Nj30+Ty2EVwX/aZ2Y2UwmZgkf4vXXuNm9jbg0ij0TQ== X-Received: by 2002:a17:903:2783:b0:1c4:313c:babc with SMTP id jw3-20020a170903278300b001c4313cbabcmr7539199plb.2.1695062994308; Mon, 18 Sep 2023 11:49:54 -0700 (PDT) Received: from hermes.local (204-195-112-131.wavecable.com. [204.195.112.131]) by smtp.gmail.com with ESMTPSA id iz19-20020a170902ef9300b001c3bc7b8816sm8661523plb.284.2023.09.18.11.49.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 18 Sep 2023 11:49:54 -0700 (PDT) Date: Mon, 18 Sep 2023 11:49:50 -0700 From: Stephen Hemminger To: Gabor LENCSE Cc: users@dpdk.org Subject: Re: rte_exit() does not terminate the program -- is it a bug or a new feature? Message-ID: <20230918114950.6be79839@hermes.local> In-Reply-To: <9d41e20b-f0b9-eba0-484c-8bafc96c5ca9@hit.bme.hu> References: <3ef90e53-c28b-09e8-e3f3-2b78727114ff@hit.bme.hu> <20230915080608.724f0102@hermes.local> <35b55d11-bb67-2363-6f0a-0fb9667ebe6d@hit.bme.hu> <20230915143305.0ac313c6@hermes.local> <930f2885-caec-7297-65f7-0959dd6d550c@hit.bme.hu> <20230917142753.596c988a@hermes.local> <9d41e20b-f0b9-eba0-484c-8bafc96c5ca9@hit.bme.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Mon, 18 Sep 2023 20:23:25 +0200 Gabor LENCSE wrote: > Of course, I will review all my rte_exit calls... It'll take a while... > > I am just curious, as I have no idea, why my old code worked all right > with DPDK 16.11. Has rte_exit() been changed since then? Older versions of the DPDK did not call eal_cleanup() and did not have service lcores. I think service lcores were new in 18.11