On Fri, 2012-05-04 at 13:49 -0700, Nishanth Aravamudan wrote: > I think it's ok for hotplug to be destructive. But I guess I'm not > entirely sure why cpusets can't retain user-inputted > configuration/policy information even while destroying things currently? > And re-instating that policy if possible in the future? Two issues here: - if you retain it for cpuset but not others that's confusing (too); - we never retain anything, if you unload a module you loose all state that was associated with it too. What makes this special? -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
