[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: struct ifnet and ifaddr handling [was: Re: Making global variables of if.c MPSAFE]
>> Otherwise (and even so), someone is likely to remove the kernel lock
>> without understanding the constraints and wind up with an interrupt
>> handler on cpu0 munging the ifnet list at the same time as a thread on
>> Anyway we should get rid of calling m_reclaim in hardware interrupt
>> as rmind said.
>> Sounds good to me! Seems like the only actual user of it in-tree is
> Really? If so, we can get rid of it easier than I expected.
> I'm looking at it!
mallocs in the below two functions can be called from interrupt context.
Can we use pool in these cases?
Main Index |
Thread Index |