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 B21B043AFB for ; Sat, 17 Feb 2024 17:59:57 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 33C76400D7; Sat, 17 Feb 2024 17:59:57 +0100 (CET) Received: from mail-oi1-f182.google.com (mail-oi1-f182.google.com [209.85.167.182]) by mails.dpdk.org (Postfix) with ESMTP id 8018B40042 for ; Sat, 17 Feb 2024 17:59:55 +0100 (CET) Received: by mail-oi1-f182.google.com with SMTP id 5614622812f47-3c135913200so1268543b6e.1 for ; Sat, 17 Feb 2024 08:59:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1708189194; x=1708793994; 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=ZAxT490HV3VH5tdG7yS3eA7H1fNdaGXl7KU3AXJVgLM=; b=kQGfZup4tpb+UXZ+WaS+LykuFBh2fYLvludfOL+uWK6HKvsfRMQrEHuz8L5YMMTiL5 xTnJxOk5nN2Ptl9jQF9OC1O5znvyoG5s2FcbWzsaUEuP++ZHBP38YjeMSVlFFqxdo28d CLDYgZf8RongTTteKhGyK6+LnbFaIVC/S3o36BwUrrd/ogS4Iod2hgh0eNN3zdJwFcmI udj0UHpqva4WntL3KqG6kMwqNDbPW8n/MBwXGvZhVdnKZps/WVq14TZMAXb40q1FDHef pYlxNI/mJzmKoN5F7sfA5emWGFyGxbLEagK0EUp8kExZCURAWGKEkN6cxTkR34rQW75w TzbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708189194; x=1708793994; 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=ZAxT490HV3VH5tdG7yS3eA7H1fNdaGXl7KU3AXJVgLM=; b=UNyh2HZiyOu2N9xQJq3JTGrPAfTgycHe04GkShGoylbWN8GyjWehhfQKE9sQ8182pL CgiL1O1XbT24DrNHZSJwBNtXbP5New5cHqPhM6Pl7RMxq8f0Nxa3zCFl+X4h+WcoY2O0 oke33PKLQFKLBDa75uH0BEBlZ2OjnVhMdek0/8tYUweYSxKezXhRaH4Bn/SJvZH/GJNn rnhO/FzfgEq167SGhbUEh+uaN4/RJtf6+B8n1PDqwpgfmTxccnIUPBZyXab7fjvgvpuY Fa/qxkM5dnOcEzwPW4DgsAtOauqEDHdQJWekbzoSnPvt95d0PNrHU9Z5umiyvxbSsizb GNrg== X-Gm-Message-State: AOJu0YxkjlNqIqIAjkbeAcLHh9/wovxq0oOMlMz6e6Ps1XajDtmnk1nd U5Hvy/oIBdZonN34R8UmTXAYA2KJs7IH5+j9jscOrzGo+TAlR0oOAI4x4Kr4Xn4= X-Google-Smtp-Source: AGHT+IHuffArKkJGYaukAqYk5xhwPyYlex8cviDe5w+f5k11IxUDXLrgAeByzqgvP6yUTlI3ML+xxQ== X-Received: by 2002:a05:6358:5e86:b0:179:2d7b:26f3 with SMTP id z6-20020a0563585e8600b001792d7b26f3mr9976577rwn.3.1708189194443; Sat, 17 Feb 2024 08:59:54 -0800 (PST) Received: from hermes.local (204-195-123-141.wavecable.com. [204.195.123.141]) by smtp.gmail.com with ESMTPSA id p1-20020a17090adf8100b00298cc4c56cdsm2012558pjv.22.2024.02.17.08.59.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 17 Feb 2024 08:59:54 -0800 (PST) Date: Sat, 17 Feb 2024 08:59:52 -0800 From: Stephen Hemminger To: Sameer Vaze Cc: "users@dpdk.org" Subject: Re: DPDK Pdump tool is not able to attach to DPDK test pmd primary application Message-ID: <20240217085952.7f8361eb@hermes.local> In-Reply-To: References: 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 Wed, 14 Feb 2024 22:44:46 +0000 Sameer Vaze wrote: > Hey Folks, > > I see the following message when I attempt to attach pdump to the testpmd sample application: > > Pdump output: > EAL: Failed to hotplug add device > EAL: Error - exiting with code: 1 > Cause: vdev creation failed:create_mp_ring_vdev:695 > > Testpmd output: > Reached maximum number of Ethernet ports > EAL: Driver cannot attach the device (net_pcap_rx_0) > EAL: Failed to hotplug add device on primary > > The primary and secondary applications were run using the following commands: > > Primary: sudo ./dpdk-testpmd --proc-type=primary --file-prefix=test -d /path/to/pmd > Secondary: sudo ./dpdk-pdump --proc-type=secondary --file-prefix=test -d /path/to/pmd -- --pdump 'port=0,queue=1,rx-dev=./rx.pcap,tx-dev=./tx.pcap' > > DPDK version: 22.11.1 > > Is this a known issue? Is there any known fix for this? > > Thanks > Sameer Vaze pdump and dumpcap can't work where the actual data transmit/receive is done in secondary process. The problem is in the design using callbacks and the way the pdump/dumpcap is initialized. The pdump/dumpcap works as an additional secondary process. At startup pdump/dumpcap communicates with primary process to enable callbacks on rx/tx but these work only in the primary process. In secondary process, there are no rx/tx callbacks.