On Friday 02 April 2010, Pavel Machek wrote: ... > > Neither of those are impossible with in-kernel code, so I'd argue that > > there's no need to keep the s2disk interface long-term. Userspace > > I disagree. > > > helpers might be necessary for the first one (to manage the network > > interface), but I already have multiple-resumes-from-the-same-image > > support in TuxOnice (and more 'crazy stuff' like support for resuming a > > different image after writing one - that can be used to switch to an > > initramfs containing the binaries needed to power down a UPS). > > The fact that it can be done in kernel -- anything can -- but whether > it should. I'd very much like to keep the 'crazy stuff' in userspace. IMO the question really boils down to what's the benefit of doing these things in the kernel vs doing them in the user space. If doing them in the kernel reduces the overall complexity of design (including the user space interface involved etc.) I don't really see why not to. Rafael _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
