Prev: [RFC v2][PATCH 04/11] perf trace: introduce special handling for pipe input
Next: blkio: IO controller stats
From: Pavel Machek on 2 Apr 2010 02:40
Hi!

>>>> So what's your long term plan then?
>>>
>>> First, improve the in-kernel thing, second, switch people to it, _then_ remove
>>> the s2disk interface (after we're reasonably sure it's not used by any major
>>> distro) and _finally_ simplify things after it's been removed.
>>
>> I'd really prefer to keep s2disk interface. It allows advanced stuff
>> like internet suspend resume (yep someone is doing it), crazy stuff
>> like multiple resumes from same image for fast booting (yep, some
>> embedded people are doing that) and might-be-useful stuff like
>> s2both...
>
> 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.
Pavel

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [RFC v2][PATCH 04/11] perf trace: introduce special handling for pipe input
Next: blkio: IO controller stats