On Mon, Jan 19, 2004 at 09:18:18PM +0100, Christophe Saout wrote: > As I said, 70 occurences of bi_next in the kernel. A lot under > /drivers/md, the elevator, bio.c setting it to NULL, the network block > device, ide-scsi, the loop driver, the umem driver, the cciss and > cpqarray driver (is setting bi_next to NULL? This looks strange or > possibly broken), the rest just walks the list (some ugly uses in ide > code and the generic walking code in blkdev.h). > > So it shouldn't be too much work if there would be an agreement to > change this. Perhaps we should start a new tree where we start making the large changes to the block layer that we need. 2.7 is looming, and we really should have prototype code to argue our case with. I don't see the point pushing this sort of thing for 2.6, there are far more interesting things to be done that require less effort. - Joe