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 78EC4425BD for ; Sun, 17 Sep 2023 08:37:22 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EB9634021E; Sun, 17 Sep 2023 08:37:21 +0200 (CEST) Received: from mail-ot1-f53.google.com (mail-ot1-f53.google.com [209.85.210.53]) by mails.dpdk.org (Postfix) with ESMTP id 6BABF4021D for ; Sun, 17 Sep 2023 08:37:19 +0200 (CEST) Received: by mail-ot1-f53.google.com with SMTP id 46e09a7af769-6c0c6370e5eso2210367a34.3 for ; Sat, 16 Sep 2023 23:37:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1694932639; x=1695537439; darn=dpdk.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=5FYOaDte96hEckbyrJBjLqhfYS+VUxjbkGB5ER3nxTI=; b=HW6gH/Jo2mXSV66SIT+gjQSlPiOJZAej2TI6Tgw0zqpK5iuPzo6Uqy7mA7a6Q4A1DJ f9QNVrK7zWbKshbhiNTsB0hlHWRbnryzXxQwrOhtClCg5Db7DdzN5nQ5ECPUTSpTrAh3 vWKdBmbFQ5BDxKmtUQ6Gm7RqRd98s1DyljIWIhiShbGypLTnpLqk+KM1TVL7z79ChSzD CXMF/Wfc+rhVSKx0vAqOaZU5IEJzkOQuzecyA1o+3HdLAj3RNOMsVevQKonUFour97L3 Q51HmirdjthshtJUg1STaze6cnidtVAcZWy/fDtNiN7AGc9r3C6u+LAr5tpZPYuKSYwI ft0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694932639; x=1695537439; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=5FYOaDte96hEckbyrJBjLqhfYS+VUxjbkGB5ER3nxTI=; b=qV4FVFNyBfAAabgyBjQl73tX8NWyh3fFSiafsJzV60Vc0rB5drwOrY4AwcSCccm0oX YxpI3dKmx0rMcxtB5CSX2Ft2xy9Wiy8lw0zRuwoEFn1M+X9CjvBXP0mRvUYSSs023q0P pB4KRphn6heKade8X+yPGfS6ITIq/2DbHPJgc+Mnc56jpCUMdaRf4SEKA07vlu/mEF0N cYpp62MIx+bvrqVlldKly9ttFxhAY52gOO8aj7vCB4lJKvF/n8OlPplrMW4a2104RR2P cThJC4uA2RlPurKMzoUiirjIEf8UV+r/8wEEoMo40HQVp6aBGXged6SBwvnHwXRd8ROa lG3A== X-Gm-Message-State: AOJu0YxDweCMCatee4YdaSY5gA54XpZBd9JS9OEEA0ehtmifPqY5d2P4 lWGss8GJphcECeG3LHNtCn8kd1xz2Uu220235+3UNowV X-Google-Smtp-Source: AGHT+IFGlNhTSMSL7kM8DQn6os6wXMMCMh7jkDT4N+GsGteZmWM4HwfyHlmdJWGlujN8IkjjzdjP/88xsA/srR++YJc= X-Received: by 2002:a54:4587:0:b0:3a1:df16:2eed with SMTP id z7-20020a544587000000b003a1df162eedmr6557167oib.30.1694932638835; Sat, 16 Sep 2023 23:37:18 -0700 (PDT) MIME-Version: 1.0 References: <20230916190119.100e3ac9@hermes.local> In-Reply-To: <20230916190119.100e3ac9@hermes.local> From: Isaac Boukris Date: Sun, 17 Sep 2023 09:37:06 +0300 Message-ID: Subject: Re: Concurrent invocations of the dpdk-dumpcap tool To: Stephen Hemminger Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Sun, Sep 17, 2023 at 5:01=E2=80=AFAM Stephen Hemminger wrote: > > On Sun, 17 Sep 2023 00:11:31 +0300 > Isaac Boukris wrote: > > > I'm testing with the 22.11.3 version code (latest LTS) but there don't > > seem to be significant changes in master. > > > > Given the above I had the hunch the ring names collide in shared > > memory, so I changed both the ring and the pool names in the dumpcap > > tool to include the pid, and with that the above scenario works fine > > as expected, is that a proper fix? > > If you have two processes trying to capture on same interface it > isn't going to work because both will be fighting over the same > ring of packets. To make it work would require more extensive changes > where multiple copies of packet are made. Specifically, the scenario of the crash is when trying to capture on different interfaces. By running more tests it seems that what fixes the crash is actually adding the pid to the name of the mem-pool (not the ring). Should I submit a patch with that?