> On Tue, Feb 13, 2018 at 2:12 AM, Yasunori Goto <[email protected]> wrote: > >> Hi, > [..] > > I would like to ask one more thing. > > > > What should nvdimm daemon do on detected events of > > bus/region/namespace/dimm ? > > IIRC, udev handles such hotplug events. > > What is relationship/roles between nvdimm daemon and udev? > > UDEV handles the hotplug events, but I imagine device topology changes > are of interest to whatever agent is going to be consuming monitor > events, or monitoring changes that an administrator makes to a > machine. My inspiration for including these events in the monitor > comes from the monitor functionality in mdadm. It has events like: > > DeviceDisappeared > RebuildStarted > RebuildNN > RebuildFinished > Fail > FailSpare > SpareActive > NewArray > DegradedArray > MoveSpare > SparesMissing > > To be clear, I'm not suggesting that all of these events need to be > supported in the first implementation of the monitor, but I want the > architecture and the user interface to be ready to support events from > any device in the topology. >
Ok, I got it. Thank you for your clarification. Bye, --- Yasunori Goto _______________________________________________ Linux-nvdimm mailing list [email protected] https://lists.01.org/mailman/listinfo/linux-nvdimm
