Date: Tue, 12 Sep 2006 21:38:17 +0200 From: Ulf Lilleengen <lulf@stud.ntnu.no> To: "R. B. Riddick" <arne_woerner@yahoo.com> Subject: Re: gvinum raid5 in production Message-ID: <20060912193816.GA32402@stud.ntnu.no> Resent-Message-ID: <20060912193943.GA466@stud.ntnu.no> In-Reply-To: <20060912193225.75860.qmail@web30310.mail.mud.yahoo.com> References: <20060912191744.GA28858@stud.ntnu.no> <20060912193225.75860.qmail@web30310.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On tir, sep 12, 2006 at 12:32:25 -0700, R. B. Riddick wrote: > --- Ulf Lilleengen <lulf@stud.ntnu.no> wrote: > > > As far as I understood GEOM it does not like to sleep in g_up or g_down > > > threads... So we cannot use M_WAITOK in gv_down()... > > What do you mean gv_down()? Gvinum does not use g_up or g_down as far as i > > can tell? > > > Ohoh... Tubby "typo"... > > "gv_down" is wrong... I meant "gv_drive_done()" > > As far as I understood GEOM it work as follows: > 1. A geom class provides a drive and several functions, that r needed to > operate that drive... > 2. Thread g_down hands down a new read/write/... request to an instance of a > geom class by using those functions (often called: ..._start()) > 3. Thread g_up hands up a completed/aborted request to the caller (a geom or > so) by using those functions (often called: ..._done()) Have a look at the CURRENT branch instead. It uses a worker queue. In RELENG_6 i can see that it used g_malloc. -- Ulf Lilleengen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060912193816.GA32402>