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 6750B432C8; Tue, 7 Nov 2023 17:41:18 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5310140E78; Tue, 7 Nov 2023 17:41:18 +0100 (CET) Received: from mail-pf1-f174.google.com (mail-pf1-f174.google.com [209.85.210.174]) by mails.dpdk.org (Postfix) with ESMTP id 940A2402D4 for ; Tue, 7 Nov 2023 17:41:17 +0100 (CET) Received: by mail-pf1-f174.google.com with SMTP id d2e1a72fcca58-6c39ad730aaso2437284b3a.0 for ; Tue, 07 Nov 2023 08:41:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1699375277; x=1699980077; 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=j/GbHtbNszt5gZmdQzK5gWXDUEzgjhRjgyvXIvlE4x0=; b=pOOWOU4zoW1RXhOHngESZGG8xdCbw6CehPit+gMcqTSGtgoTV1ci8NeelnNa970n03 oFQEOqFvuXiB2YUrfXLkEWWyuCKhJAcbyMYU1htmWy+/msGfPLAyaV4A04+aUt9bT4fl UKmQwtO8x1rIQbIk6WTS8FxUY9JeOcnOe776C9YcTtUL6ARI7f6yCTguHQISE1X0o1jI foT94eRRSoVXizBSqta+e1f04dQO5w6umVXx/4B8pyG3xbWY1Qmakyd4EKMIl1m7WVUb T/bXwnEZmPfe4vh/DCeesqi/TA3jFXBXzuKtEbQPg27B3XwcRpjJxRha3Gh0e0Dnd+Xn 9hBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699375277; x=1699980077; 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=j/GbHtbNszt5gZmdQzK5gWXDUEzgjhRjgyvXIvlE4x0=; b=xINdNKMQrPeMK375IvoVFDJp/GAO6kcQ2SiuckCUs3FC3jKFxlzFnm7YhupfVQZ1CV FwQHX23gjHCcXHVAz/ClROwPl3oEuk827sAUzA7MK2b0EhGZ977sKNxW5XS5MTwDwbuN /HblFz6A2wKsCgyrZi21LX4UnjfamZHWDXPJkoZS/nLGMEbZk9nDQi6ZqbSLkl+Bp+Sx QodGAsFVVoVgnuO7XYBTmmv8eIW2PSGi5R4N5TvTToPXhN6xpCWUWOGQpALSXehCNRsA pWuv/DHW6VgzNrojTq6mMDy3hnGWFDp5axpo1aIkNPqAyNEQe1mDe+lxHL01IMks3Q3s u1EQ== X-Gm-Message-State: AOJu0YyprLD5aMkMeCrAZIPz3t/bnkuB8iW9Qc8c8p/cMFdRslgKXQAt yNH/mWuVuhRJvky3062aVUAi2g== X-Google-Smtp-Source: AGHT+IEQaH9r+xcK7j88MXgp4ibFcom8zildKVOIM58MvbqWQYQznNWesvs/CerkJFjFzR68UtfgMg== X-Received: by 2002:a05:6a00:93a5:b0:6c3:703a:c394 with SMTP id ka37-20020a056a0093a500b006c3703ac394mr11720346pfb.27.1699375276728; Tue, 07 Nov 2023 08:41:16 -0800 (PST) Received: from hermes.local (204-195-123-141.wavecable.com. [204.195.123.141]) by smtp.gmail.com with ESMTPSA id o20-20020a056a001b5400b006be22fde07dsm7416000pfv.106.2023.11.07.08.41.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Nov 2023 08:41:16 -0800 (PST) Date: Tue, 7 Nov 2023 08:41:13 -0800 From: Stephen Hemminger To: Morten =?UTF-8?B?QnLDuHJ1cA==?= Cc: "David Marchand" , , Subject: Re: [PATCH] dumpcap: fix mbuf pool ring type Message-ID: <20231107084113.1bff7d9e@hermes.local> In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9EFE8@smartserver.smartshare.dk> References: <20230804161604.61050-1-stephen@networkplumber.org> <98CBD80474FA8B44BF855DF32C47DC35D87C27@smartserver.smartshare.dk> <20231106112331.690cc454@hermes.local> <98CBD80474FA8B44BF855DF32C47DC35E9EFE6@smartserver.smartshare.dk> <20231106183618.79ab6f93@hermes.local> <98CBD80474FA8B44BF855DF32C47DC35E9EFE8@smartserver.smartshare.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Tue, 7 Nov 2023 08:22:37 +0100 Morten Br=C3=B8rup wrote: > > > > > > Or are you saying that if they want to use dumpcap, they must choose = =20 > > a thread safe pool type for their application (regardless if the > > application is single-threaded or not)? > >=20 > > There is no command line of EAL nature in dumpcap. > > This is intentional. > > QED: overriding default pool type is not going to be a possible =20 >=20 > The preferred mbuf pool type can configured in the primary process by EAL= params. If so configured, it is stored in a memzone named "mbuf_user_pool_= ops". > And if it is set there, the secondary process will also use it as its pre= ferred mbuf pool type. If user decides to use a thread unsafe mempool, wouldn't it break in every = PMD as well.