Date: Tue, 12 Sep 2006 21:18:14 +0200 From: Ulf Lilleengen <lulf@stud.ntnu.no> To: "R. B. Riddick" <arne_woerner@yahoo.com> Cc: freebsd-geom@freebsd.org Subject: Re: gvinum raid5 in production Message-ID: <20060912191744.GA28858@stud.ntnu.no> In-Reply-To: <20060912184453.33677.qmail@web30313.mail.mud.yahoo.com> References: <1158086253.4506fe6d6d6fe@webmail.ntnu.no> <20060912184453.33677.qmail@web30313.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On tir, sep 12, 2006 at 11:44:53 -0700, R. B. Riddick wrote: > --- Ulf Lilleengen <lulf@stud.ntnu.no> wrote: > > Quoting Mark Bucciarelli <mark@gaiahost.coop>: > > > Is anybody using gvinum raid5 in production with 6.1-release? How is > > > it going? > > > > About the PR's you found I'm not sure of what's a gvinum bug or not of > > them, but at the thing about not checking NULL pointers for g_malloc is > > because when passing the M_WAITOK flag to g_malloc (or kernel malloc > > for instance), it is guaranteed to not return NULL because the flag > > tells malloc to wait for resources to be freed. > > > 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? -- Ulf Lilleengen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060912191744.GA28858>