Date: Wed, 16 Jan 2002 11:09:19 -0800 From: Alfred Perlstein <bright@mu.org> To: Dan Moschuk <dan@FreeBSD.ORG> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, arch@FreeBSD.ORG Subject: Re: M_SHORTWAIT, the md driver and errno Message-ID: <20020116110919.D26067@elvis.mu.org> In-Reply-To: <20020116114805.L7831@spirit.jaded.net>; from dan@FreeBSD.ORG on Wed, Jan 16, 2002 at 11:48:05AM -0500 References: <20020116012950.C7831@spirit.jaded.net> <43818.1011165127@critter.freebsd.dk> <20020116114805.L7831@spirit.jaded.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Dan Moschuk <dan@FreeBSD.ORG> [020116 08:48] wrote: > > | >I'm fixing up the md driver to use the M_SHORTWAIT flag when allocating > | >memory. In the event that our request times out, what errno should the > | >driver return? > | > | Good question, I guess EIO is the "make sure not to break anything" > | choice, but obviously ENOMEM would make more sense. > > ENOMEM would make the most sense, I just wasn't sure you were "allowed" to > return that for write calls. > > EIO kind of sucks; seeing an "Input/output error" while writing to a > memory disk will probably result in people incorrectly thinking that they > have bad ram. I think EIO is probably more correct with a rate limited console message explaining what happened. Also, I think that the timeout should be configurable and users should have the option to turn it off. I also think that the timeout should be relatively long, on the order of 30 seconds at least. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020116110919.D26067>