"Steven M. Bellovin" <smb@cs.columbia.edu> writes:
>> > FWIW, I do _not_ have BUFQ_READPRIO in either of my kernels that
>> > this manifests itself.
>> 
>> My point was that I think that the behavior that BUFQ_READPRIO
>> formerly prevented on my machines is now happening again for me.
>> 
> Which is why I asked if the problem just started for him.  If it's new,
> it has nothing to do with BUFQ_READPRIO, since if it were BUFQ_READPRIO
> he would have been experiencing it all along.

Good point.

Perry