--- Begin Message ---
On Fri, May 20, 2022 at 12:36 PM Guy Harris wrote:
> If it's putting them in non-blocking mode, and using some
> select/poll/epoll/etc. mechanism in a single event loop, then the right
> name for the API is pcap_setnonblock(). There's no need for an eventfd to
> wake up the
--- Begin Message ---
On May 20, 2022, at 10:56 AM, Bill Fenner via tcpdump-workers
wrote:
> I'm helping to debug a system that uses many many pcap handles, and never
> calls pcap_loop - only ever pcap_next.
Both pcap_loop() and pcap_next() ultimately go to the same place.
Note, BTW, that pcap
--- Begin Message ---
I'm helping to debug a system that uses many many pcap handles, and never
calls pcap_loop - only ever pcap_next. We've found that each pcap handle
has an associated eventfd, which is used to make sure to wake up when
pcap_breakloop() is called. Since this code doesn't call p
