Re: IDE Driver (Raw Interface) Questions

Alan Cox (alan@lxorguk.ukuu.org.uk)
Tue, 21 Dec 1999 22:14:15 +0000 (GMT)


> I want to implement the same locking strategy _without_ going through
> ll_rw_block(). That's the whole point -- I don't want to utilize that
> function as a mechanism for writing to disk. If I used ll_rw_block(),
> I might as well do that for all disk types. It's obviously the wrong
> way to go in a system crash scenario, which is where I'm going to be
> utilizing the code.

Ok. System crash is a bit different. You could reinit the spinlock and
wipe the request queue at this point however. That would let you reuse the
existing code but slam it back into a hopefully known state first.

> I'm not saying "ignore what's in buffer cache", just that if this code
> gets executed, it's very doubtful what was in the buffer cache really
> would have ever made it to disk. You'll be "Oops" or "Aiee"ing.

If your oopsed badly the buffer cache is best left unwritten from experience.

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/