All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Stephen Hemminger <stephen@networkplumber.org>
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
Date: Thu, 10 Oct 2024 03:24:42 +0100	[thread overview]
Message-ID: <c22ef2e6-d857-44d0-ba4c-92bc8f167eb5@amd.com> (raw)
In-Reply-To: <20241009192121.5e77260f@hermes.local>

On 10/10/2024 3:21 AM, Stephen Hemminger wrote:
> 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!
> 

Thanks for confirming. I assume it is same with the 'iphlpapi' that
windows uses.

Let wait a little more, it would be good if we get a test result from
Ofer first.


  reply	other threads:[~2024-10-10  2:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 16:10 [PATCH] net/pcap: use pcap_next_ex to track errors Stephen Hemminger
2024-10-10  2:14 ` Ferruh Yigit
2024-10-10  2:21   ` Stephen Hemminger
2024-10-10  2:24     ` Ferruh Yigit [this message]
2024-10-10  2:34       ` Stephen Hemminger
2024-10-13 15:47 ` Ferruh Yigit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c22ef2e6-d857-44d0-ba4c-92bc8f167eb5@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=ofer.d@claroty.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.