No subject

Thu Aug 19 10:34:18 PDT 2010

point we are creating a couple of C# objects in order to turn the =
unmanaged=20
winpcap structures into C# managed objects. After that, we are =
enqueueing these=20
objects in an own circular buffer and then another thread-pool is =
unbuffering=20
this information. We have figured out that our circular buffer is not =
discarding=20
any packets. &nbsp; Our big concern is that currently we are =
experiencing=20
Winpcap issues in our application which has peaks of 25 concurrent =
calls, and if=20
we think that we might get peaks of 200 concurrent calls in the future, =
I'm not=20
sure that some application's performance improvement will make a big =
difference=20
than today's performance. We think that maybe a better approach would be =
to open=20
several times the sniffed interface and, for each one, sets the =
respective=20
IPAddresses and Ports' filter. &nbsp; Based on what I've told =
you, we=20
want to know your opinion: &nbsp; a) Do you think the fact of =
opening=20
several times the same interface and setting better filters will be a =
good=20
approach? &nbsp; b) How many concurrent winpcap handlers (for one=20
interfaces) we may have opened at the same time? &nbsp; c) We think =
that if=20
we open the interface several times there will be several winpcap kernel =
ring=20
buffers. What size do you think would be the best for each of these =
kernel ring=20
buffers? If we think in having Kernel ring buffers of 5 MBytes, and 200=20
concurrent calls, we would need 1 GByte of memory dedicated to Kernel =
Ring=20
Buffer. This memory requirement is not a problem anyways. &nbsp; d) =
Do you=20
think that we should concentrate our effort in trying to improve our=20
application's performance? We are just creating C# objects... That =
shouldn't=20
consume much time. Thanks in advance for your help. Damian =

Nardelli - C/C++/.NET Software Developer.<BR><BR>
<P>
<HR>

<P></P>_______________________________________________<BR>Winpcap-users =
mailing=20
list<BR>Winpcap-users at winpcap.org<BR>https://www.winpcap.org/mailman/list=
info/winpcap-users<BR></BODY></HTML>

------=_NextPart_000_02DA_01CB3F8E.E3E25D00--