On Fri Nov 25 01:47:12 EST 2011, cinap_len...@gmx.de wrote: > drivers should be pretty portable. > > there are more drastic changes like the eqlock function > that touched many places. its basicly a normal qlock() > that can error() out when the process gets a note or > gets killed.
ha! i've written this function independently a few times. and applied it to a few well-chosen places. i stopped short because i wondered if postdawn (e.g. after schedinit() is called), qlock() shouldn't always be an eqlock(). i see this problem most often with networking code. the the first reader is interruptable, but readers 2..n are not. i'd love to hear other opinions on how to solve this problem. - erik
