Gianluca, Thanks very much for your quick response, we are very eager to have WinPcap work on a SMP machine. We have a dual processor machine in house, and have been testing, but have not caused it to fail yet. We are considering looking into the WinPcap code ourselves to try and make it SMP safe, we would love to work in conjunction with you on this, either by helping to test your code, or by making the changes ourselves with your input. Can you give us any guidance as to what approach we should take, and what areas we should look at to make the code SMP safe? Since we have so far been unable to make the code fail, can you give us some idea of how to increase the likelihood of a failure( i.e. Is their some way to make it more likely that the driver will switch between processors ). If we cannot reproduce the problem we will not know if any changes we make will fix the problem. Thanks Jay
> -----Original Message----- > From: Gianluca Varenni [mailto:[EMAIL PROTECTED]] > Sent: Friday, August 30, 2002 2:40 AM > To: [EMAIL PROTECTED] > Subject: Re: [WinPcap-users] FW: SetProcessAffinityMask > > > > ----- Original Message ----- > From: "Jay Sillars" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, August 30, 2002 12:40 AM > Subject: [WinPcap-users] FW: SetProcessAffinityMask > > > > > I understand that win-pcap has not been written or tested to work on > > SMP machines. > > Is there any way to set the processor affinity for my process and or > > the winpcap device driver so that it will be limited to > using a single > > processor? > > It is not possible to set the "driver" affinity mask. > > I use "..." for the driver, since the driver is different > from a user level > program, it does not have a main or such. > > > > If I use SetProcessAffinityMask in my application will it have any > > affect on which processor the device driver uses? > > We will only have one process using the driver. > > Absolutely no! It affect the driver function that trasfer > data from kernel > level to user level (because it runs in the context of the > calling thread, > that is to say the user application). Instead, the function > that is called > by the OS and receives packets from the network card runs in > the "context of > a system thread" (quite complicated things...), in practice > it can run on > every processor. > However, I think we will work on the SMP issue in the next > months (do not > ask me when, I don't know). > > GV > > > > > > > > > > > ====================== > This is the WinPcap users list. It is archived at > http://www.mail-archive.com/[email protected]/ > > To unsubscribe use > mailto: [EMAIL PROTECTED]?body=subscribe > ====================== > > > > > > > ================================================================== > This is the WinPcap users list. It is archived at > http://www.mail-archive.com/[email protected]/ > > To unsubscribe use > mailto: [EMAIL PROTECTED]?body=unsubscribe > ================================================================== > ================================================================= This is the WinPcap users list. It is archived at http://www.mail-archive.com/[email protected]/ To unsubscribe use mailto: [EMAIL PROTECTED]?body=unsubscribe =================================================================
