On Thu, Aug 27, 2015 at 03:43:52PM +0200, J. Hannken-Illjes wrote: > > This was the intention with "bufq_peek". All current bufq strategies > seem to keep the current buf the same over "bufq_peek .. bufq_get" > even if more work comes in via "bufq_put".
The whole bufq_peek, use_the_buffer_for_something, bufq_get sequence, must then run serialized and allow the use part to recurse into the start routine. This works fine as is in almost all drivers (dksubr is used by only 3 so far) with KERNEL_LOCK and nestable splbio()/splx() calls. How do you suggest to do it without? -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."