There is no difference between pcap_next_ex and pcap_loop/pcap_dispatch even in that case. Please consider that when dumping to disk, the bottleneck is
1. the disk itself 2. the filesystem 3. the fact that pcap_dump_open/pcap_dump use the standard FILE I/O routines. Have a nice day GV ----- Original Message ----- From: "Srivats P" <[email protected]> To: <[email protected]> Sent: Tuesday, November 03, 2009 3:34 PM Subject: Re: [Winpcap-users] pcap_loop()/pcap_breakloop() problem > Yes, performance wise? > > On Tue, Nov 3, 2009 at 10:09 PM, <[email protected]> > wrote: >> GV, >> >> How does using pcap_next_ex() compare with pcap_loop() - >> performance-wise? >> >> --GV-- >> There is no performance penalty, we have used pcap_next_ex at >> multigigabit >> rates. >> --GV-- >> >> >> Is there any difference if I capture to file i.e. using >> pcap_dump_open()/pcap_dump() >> >> --GV-- >> What kind of difference? performance wise? >> >> Have a nice day >> GV > _______________________________________________ > Winpcap-users mailing list > [email protected] > https://www.winpcap.org/mailman/listinfo/winpcap-users _______________________________________________ Winpcap-users mailing list [email protected] https://www.winpcap.org/mailman/listinfo/winpcap-users
