Re: RFC: Project geom-events

Hello, Andrey.
You wrote 5 =CF=CB=D4=D1=C2=D2=D1 2011 =C7., 9:07:16:

> It seems that you could change only geom_dev.c to get most of what you wa=
nt.
> Actually, the part of your changes related to the DISCONNECT events, and
> maybe DESTROY events could be implemented in the geom_dev.
  Does geom_dev knows all needed bits of information to report? It seems to=
 me,
that it isn't.
  I mean:

   (1) Class and name of GEOM which is affected.
   (2) Name of provider which is affected.
   (3) Name of underlying provider which is lost (consumer from
       reporting GEOM's point of view).
   (4) Resulting state of affected provider (fixable, alive, dead).

  Yes, geom_dev knows name of FAILED provider, but does it knows all
 other? I'm affraid -- not, or I don't understand how generic
 mechanism could now, that geom_stripe could not lose components and
 still be fixable, and gome_mirror could.

  Additionally, some GEOM classes could throw away faulty consumers before
 they disappear from geom_dev point of view.

  Actually, DESTROY could be observed without my changes at all --
 message from DEVFS about removing entry :) But, again, this
 notification will not contain name and class of GEOM, only provider's
 name (devfs entry).

--=20
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"