From owner-freebsd-arch Tue Jan 15 23:14:41 2002 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 845DE37B416; Tue, 15 Jan 2002 23:14:39 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id g0G7C7U43820; Wed, 16 Jan 2002 08:12:08 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dan Moschuk Cc: arch@FreeBSD.ORG Subject: Re: M_SHORTWAIT, the md driver and errno In-Reply-To: Your message of "Wed, 16 Jan 2002 01:29:50 EST." <20020116012950.C7831@spirit.jaded.net> Date: Wed, 16 Jan 2002 08:12:07 +0100 Message-ID: <43818.1011165127@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020116012950.C7831@spirit.jaded.net>, Dan Moschuk writes: > >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. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message