I guess that I should have phrased my question differently. "Multi-threaded" can have multiple meanings. 1. Two threads can simultaneously access the same SNMP session pointer. 2. Two threads can simultaneously talk to the same SNMP agent via different session pointers (unique to each thread). 3. Two threads can simultaneously talk to *different* SNMP agents via different session pointers (unique to each thread).
I am not interested in #1; rather, I am interested in a combination of #2 and #3. My main concern is that net-snmp not break when two threads are doing their own v3 things at the same time. Ideally, I want two threads to talk to the same agent via different session pointers. Essentially, each thread would do its own "snmp_sess_open" call, and it just so happens that they would each attempt to talk to the same IP address. In *that* context, do you have any comments on the thread safety (in senses #2 and #3) of net-snmp? Remember, at this point, our tool is using a mutex for *all* v3 calls, drastically reducing performance as v3 is used more. ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
