The batching between kernel level and user level is the default behavior of
WinPcap, and is done to minimize the number of context switches and
therefore increase performance. You can disable it using the
PacketSetMinToCopy
function(http://winpcap.polito.it/docs/docs31beta3/html/group__packet32.html
#a11). The default value for nbytes is (if I remember well)
16K. 0 forces the driver to return as soon as a packet is available.

Loris

----- Original Message ----- 
From: "Dmitri Krasnenko" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, June 14, 2004 3:16 AM
Subject: [WinPcap-users] WINPCAP PACKET DELIVERING DELAY


> During development of my WinPcap-based application I pay attention that
> WinPcap deliver the data ( invokes the packet handler function first time
> ) only after reception of first 150 - 200 packets.
>
> How I can affect and minimize to zero, if it possible, tis delay?
>
> In my application I open the adapter in promiscuous mode, with zero
> timeout and call the pcap_loop() function.
>
>
>
> ==================================================================
>  This is the WinPcap users list. It is archived at
>  http://www.mail-archive.com/[EMAIL PROTECTED]/
>
>  To unsubscribe use
>  mailto: [EMAIL PROTECTED]
> ==================================================================



==================================================================
 This is the WinPcap users list. It is archived at
 http://www.mail-archive.com/[EMAIL PROTECTED]/

 To unsubscribe use 
 mailto: [EMAIL PROTECTED]
==================================================================

Reply via email to