> For what it's worth, it doesn't sound like that's > what he means. > Instead, the driver is "health checked" in some way > and deliberately > unloaded and reloaded if it's not working.
Yes indeed IIRC that's the purpose of this feature. > Rather than being an additional stress-test (which is > what the DEBUG > behavior in Solaris is), it sounds like the intent is > to work around > bug-ridden drivers. If so, that's verging far too > close for my taste > to continuing operation after internal consistency > has been lost and > risking data corruption. > Maybe that could depend on the module/driver. I agree it'd be better to stop working if there is a problem in the filesystem kernel module. But we could imagine some other drivers (e.g. sound card driver) where this behaviour (unload/reload if it doesn't respond) is "safe". Drivers could be "marked" (it'd be a user choice) as safely reloadable. This feature made me think "yep that's a nice idea" when I read about it. I did not think much more about it, and maybe it's not that cool, it can of course be discussed. That's what I thought about when starting this thread. If people write down what they'd like to see in Solaris, this could give people some ideas to start new cool projects or improve some others. A kind of suggestion box. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
