From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 76B0D43069;
	Tue, 15 Aug 2023 05:12:18 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 05400427E9;
	Tue, 15 Aug 2023 05:12:18 +0200 (CEST)
Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217])
 by mails.dpdk.org (Postfix) with ESMTP id 732EF41104
 for <dev@dpdk.org>; Tue, 15 Aug 2023 05:12:16 +0200 (CEST)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by dfw.source.kernel.org (Postfix) with ESMTPS id D1D4360B18;
 Tue, 15 Aug 2023 03:12:15 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 07460C433C7;
 Tue, 15 Aug 2023 03:12:14 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
 s=k20201202; t=1692069135;
 bh=i0xtNxrJstAWnMoDdodp0wJWeAEHC6TYkS+ugPqmQEA=;
 h=Subject:From:To:Cc:Date:In-Reply-To:References:From;
 b=bpfjTlMjdna24CdBGkF5uwoX5fX59EdX6HfZvMQ1uHqpKiHnpUHjReQ3qZ4ftMjkY
 F/mkxXWp5sV0V/+svnkvzvd7+EQ+xOnG+eNqz1GjdegJYfPNhMZMY3ofW+//koznVV
 gBl9vOJ+zepE2Yy82wtfxqbIZ8TF1LMhF0amel7T4e4MMf5Rg4e3O9lUUuhOdy1pGX
 G8HSOXx6AxaJMreL3Hty/L4VLxTpyBGe3A6IAXLmU8uiyewgz6Wm8X16Wojc3sqDN9
 SsuAvoZaRUicZKMFUuN8/ycKiQpmIZttntuMF5ifTOeyeD64rCApikwMwMFOieoWKt
 H44YqiqQ5MdpA==
Message-ID: <361b539e74a91646388ff56cd784653c28c54963.camel@kernel.org>
Subject: Re: [PATCH v1 0/7] support reinit flow
From: Sinan Kaya <okaya@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Date: Mon, 14 Aug 2023 23:12:09 -0400
In-Reply-To: <20230814191203.58a427d1@hermes.local>
References: <20230815013826.1288972-1-okaya@kernel.org>
 <20230814191203.58a427d1@hermes.local>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5-0ubuntu1 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

On Mon, 2023-08-14 at 19:12 -0700, Stephen Hemminger wrote:
> On Mon, 14 Aug 2023 21:38:19 -0400
> 
> okaya@kernel.org wrote:
> 
> 
> 
> > From: Sinan Kaya <okaya@kernel.org>
> > We want to be able to call rte_eal_init() and rte_eal_cleanup()
> > APIs back to back for maintanance reasons.
> 
> 
> Why?
> 
> This change exposes lots of drivers, API's and other things to
> untested code paths.
> 
> If you just want to do a hard restart, maybe just reexecing the same
> application would
> 
> be better.

It is not always ideal to reinitialize a DPDK process. Memory needs
to be reinitialized, hugetables need to warm up etc.

Given the cost of change is not huge, I believe this will be
important contribution for certain application types.
Changeset is not doing anything different from what already exists.