Re: sd driver NOT_READY behavior / was Re: How does the disk buffer cache work?

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Wed Jan 01 2003 - 16:32:24 EST

Next message: Marc-Christian Petersen: "set_current_state(); vs current->state = bla;"
Previous message: Andre Hedrick: "RE:Re: Re: Why is Nvidia given GPL'd code to use in closed source drivers?"
In reply to: Matthew Zahorik: "sd driver NOT_READY behavior / was Re: How does the disk buffer cache work?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, 2003-01-01 at 19:19, Matthew Zahorik wrote:
> What is the correct behavior that I should implement?
>
> a. if !removable && not ready then error
> b. if not ready then increase count until threshold then error
> c if not ready then error
> d. none of the above

I would go for a time limit (you don't want to keep spamming the same
command but to poll politely really IMHO)

-
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/

Next message: Marc-Christian Petersen: "set_current_state(); vs current->state = bla;"
Previous message: Andre Hedrick: "RE:Re: Re: Why is Nvidia given GPL'd code to use in closed source drivers?"
In reply to: Matthew Zahorik: "sd driver NOT_READY behavior / was Re: How does the disk buffer cache work?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Jan 07 2003 - 22:00:15 EST