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 5468D45482 for ; Mon, 17 Jun 2024 16:44:27 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 49CC840698; Mon, 17 Jun 2024 16:44:27 +0200 (CEST) Received: from mail-pf1-f169.google.com (mail-pf1-f169.google.com [209.85.210.169]) by mails.dpdk.org (Postfix) with ESMTP id 2AC83406BC for ; Mon, 17 Jun 2024 16:44:16 +0200 (CEST) Received: by mail-pf1-f169.google.com with SMTP id d2e1a72fcca58-70436048c25so3364091b3a.0 for ; Mon, 17 Jun 2024 07:44:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1718635455; x=1719240255; 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=iMNfsxsmyk7ZIQidSvpe2iBFqpJNN3LpisY1xfsJS/Q=; b=exEu/cfDsFgwt35KnWVaOGKHNXNdVGwWDa5qajD53EOYKVTA9A85nVlH8fxSe97bUx VWTEF/4LSCKu8/BTp195fOI4uOqXE/8UyR9S4UTxaVFylCgou4/NCFOU+VYZlp5XOhbE 1O9xeTZ6cfVINYzdI1uvjVA6Dc95Sv3WIjfGs0F10FgMPSu+U8xutM2h1yZrs8H7a4Xm 0Y9g5pewE+CO8VyGufhPcAVj3orlxqBJg+D5hlsQLjkTiyiDZOPVGKAy6K3rL1xvvXu/ 6y6ZIuWxU1HRELTUFpLUHM6reanhPGleTGBmVqLFw4rZGfAC/R8L9biLU2lkTQfdCOpJ 4tUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718635455; x=1719240255; 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=iMNfsxsmyk7ZIQidSvpe2iBFqpJNN3LpisY1xfsJS/Q=; b=Q0YT6AEPkG/0bcrn/toZrSJf3AgdorH+mV5iWYGDxBUP79KNdes9RUAsSMZs9fPFBb P7s/V7d7sB6/v3jeOxkTrrNawRcow7DeUni2ftjL2bNJepn07sPz9DzOJz3Y4NCuwyeD JL+Ol02lrG5MWfWQZ1kuWcTVkrlj28FPFUJvTK/vEeuL6SpegVrJTldoxQXoJTXCKXMn cz2fBGmmApaNxpIzwlQLctl13/VYo0MjAH61BFDMojF3SPx3od67wikaF+BBCL6rs/ZA PoqOUbVsuUlsydaAI9HDrz5/g6+Is75Wf+jLTyas7QhUxqa5pVj8plc1pIQQFanVVde6 T89w== X-Gm-Message-State: AOJu0YzLNVYXUC87KZGzBNd3ypz0MZWb2QaUIu8RXJGkOnjcOupSWhAX 5RzZqbJ1cY4W2hHeq3zit+lYOYw1C66NFjFakU5+DCkr4r9FelNKyN3tVrSJriXWNQ652ABGhoQ i X-Google-Smtp-Source: AGHT+IFiAWknyvOpfwX0WDsubXdZlaBie3RHeniocUlIErnLEeEw5BqaeerE5Q8Ku5yU+JYV37MtMA== X-Received: by 2002:a05:6a00:130a:b0:704:2ba2:de31 with SMTP id d2e1a72fcca58-705d6fb9690mr10502284b3a.0.1718635455226; Mon, 17 Jun 2024 07:44:15 -0700 (PDT) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-705ccb6b9b3sm7384035b3a.166.2024.06.17.07.44.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 17 Jun 2024 07:44:15 -0700 (PDT) Date: Mon, 17 Jun 2024 07:44:13 -0700 From: Stephen Hemminger To: Isaac Boukris Cc: users@dpdk.org Subject: Re: dumpcap: weird failure with six IPv6 hosts in the filter Message-ID: <20240617074413.46af9fca@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 Mon, 17 Jun 2024 10:11:47 +0300 Isaac Boukris wrote: > Hi Stephen, > > For instance, the following filter fais as follows (if I omit one host > it works): > -f "host 1::1 or host 1::1 or host 1::1 or host 1::1 or host 1::1 or host 1::1" > > EAL: Error - exiting with code: 1 > Cause: Packet dump enable on 0:0000:13:00.0 failed Connection timed out > > On the server side I see: > Jun 16 15:17:08: EAL: failed to send to > (/tmp/dpdk/rte/mp_socket_262131_4a103955de0b7a) due to No such file or > directory > Jun 16 15:17:08: pdump_server(): failed to send to client:No such file > or directory > Jun 16 15:17:08: EAL: Fail to handle message: mp_pdump > > Then subsequent requests fail with (even with no filter): > pdump_register_rx_callbacks(): rx callback for port=0 queue=0, already exists > > I debugged the dpdk-mp-msg thread with gdb, as far as I can tell it > hangs an awful lot of time on rte_bpf_load() (~15 secs in my env), so > the client times out and by the time the server tries to respond the > client socket doesn't exist anymore. > > Thoughts? > > Thanks! What is the resulting bpf code? Looks like a BPF bug with larger programs.