Correct.  I am still reviewing drivers and kernel code to ascertain 
whether I am not leaving any holes.  I have spliced it as a non-obtrusive 
implementation that preserves the existing code with no changes.  
Some of the drivers may have problems if they cache the head address
of the current list.
> 
> 2.5 has this done much more cleanly (of course I'm very biased). See the
> deadline I/O scheduler patch I've posted before, stuff like this can be
> done a lot cleaner there. Internal I/O scheduler structures are
> completely hidden from drivers.
> 
2.5 would be nice, but 2.4.X needs it too and this is the kernel we are 
using for our development and testing, so we will need it there.  
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/