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 054F345AFB; Thu, 10 Oct 2024 04:21:27 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C614E402E1; Thu, 10 Oct 2024 04:21:26 +0200 (CEST) Received: from mail-pj1-f46.google.com (mail-pj1-f46.google.com [209.85.216.46]) by mails.dpdk.org (Postfix) with ESMTP id 0F61C4029A for <dev@dpdk.org>; Thu, 10 Oct 2024 04:21:24 +0200 (CEST) Received: by mail-pj1-f46.google.com with SMTP id 98e67ed59e1d1-2e0d9b70455so379929a91.3 for <dev@dpdk.org>; Wed, 09 Oct 2024 19:21:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1728526884; x=1729131684; 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=Uwu8M2dby6tXa1RD+v6cCq4F1+pubwWnAXx375d3HH4=; b=JqTvaO+je7+EDIJTHJnuCj71pdcqYc4pxgDnpdVDxD8I9uO2r4ypmOTnKmSpnyzaCA anWb3qYZFBDJiJqeiv+NxWSi6VJ0gPepsK+S53aFg8GbrqrTMP1l6cIU+reAZ5orca8F ksbEUydarmyghtRh0Z9Nb2ua/20n3sSi4r5dY6S508VXgvH3AyMTXC4NE4V+9P7ggfsg 2nvofNkUO2jRdNS9nxAirXyhPEcV2UXWnE5no/3nEb0PG4n+qstzQUt+UZnYH7Brx0aI YZrXa4YUIkHBIPse9Jb0qbHJjTQBVp1/kKzVsQ7Z8ygPKiaIX7gWp7plg/wMk8zMK5TY FlHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728526884; x=1729131684; 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=Uwu8M2dby6tXa1RD+v6cCq4F1+pubwWnAXx375d3HH4=; b=c4gS3w4XSwVoQOdXkly6gF0+UZ3C21FcQzSl2qRMQ8B8vXszXx8x3p+vcz+S6HEy5z YlXub06nuVc4DA/D+kWyHR/hy5TT0OaKumw3Jwo1EviV0w+g19s5K3MEKSHmoCh4PC8l QgCI6Yn2b7KXpeaQetnY0d9q92J4Ee6kWIYYAz/ejXXlEwMu4bkQe7iupjkslbi2rd8I 6AqwYBBo2ALqTHWlofG+bP6BAI/FSONmU5xCHM4YZvm0YFQHdOxBnwoMoS7jU9FWgHW+ mIcY4452z2T/8cNA/meupx7zeLmumRC1oJxz4L01JFvmrbcwPvLS9Dyb4fYfSwBeW+ib GPwQ== X-Gm-Message-State: AOJu0YwfwDXBhVNkQLLjam2URSHdZM3jO4EQk7Da/sO/JtCx/Sv2Zp+x EVXXn0QWM6QAnU+w5CbuaUSwen8S2riX9sKzPlhbS95JUKQjaWT+NECvvY4Uhug= X-Google-Smtp-Source: AGHT+IFMhPlTqOxPIJK/R/pbEseYImW8WSAyR7pKT+kNT5NxqzEnN94WSEwm4vmzowPOnSdPGBMrsw== X-Received: by 2002:a17:90a:178e:b0:2e2:cc47:ce1a with SMTP id 98e67ed59e1d1-2e2cc47ce65mr1506442a91.1.1728526884082; Wed, 09 Oct 2024 19:21:24 -0700 (PDT) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2e2a5712699sm2436866a91.29.2024.10.09.19.21.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Oct 2024 19:21:23 -0700 (PDT) Date: Wed, 9 Oct 2024 19:21:21 -0700 From: Stephen Hemminger <stephen@networkplumber.org> To: Ferruh Yigit <ferruh.yigit@amd.com> Cc: dev@dpdk.org, Ofer Dagan <ofer.d@claroty.com>, Tyler Retzlaff <roretzla@linux.microsoft.com> Subject: Re: [PATCH] net/pcap: use pcap_next_ex to track errors Message-ID: <20241009192121.5e77260f@hermes.local> In-Reply-To: <5fd99bc4-cad2-4a40-b4cd-6d6332cc491b@amd.com> References: <20240905161129.73553-1-stephen@networkplumber.org> <5fd99bc4-cad2-4a40-b4cd-6d6332cc491b@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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 Thu, 10 Oct 2024 03:14:48 +0100 Ferruh Yigit <ferruh.yigit@amd.com> wrote: > On 9/5/2024 5:10 PM, Stephen Hemminger wrote: > > Use pcap_next_ex rather than just pcap_next because pcap_next > > always blocks if there is no packets to receive. > > > > Hi Stephen, > > Do you know if using 'pcap_next_ex()' (instead of 'pcap_next()') has any > dependency impact? > Like can we rely that all libraries that support 'pcap_next()', also > supports 'pcap_next_ex()'? The code depends on libpcap, and that API has been in pcap since the early days. See it in a version from 2003!