On Čt 01-06-06 16:35:12, Jon Smirl wrote:
> On 6/1/06, D. Hazelton <[email protected]> wrote:
> >> > 5) The system needs to be robust. Daemons can be killed by the OOM
> >> > mechanism, you don't want to lose your console in the middle of trying
> >> > to fix a problem. This also means that you have to be able to display
> >> > printk's from inside interrupt handles.
> >
> >Point of disagreement. Tons of userspace helpers isn't a good choice.
>
> Where do you get 'tons'? There will probably be one for initial reset,
> one for VESA based mode setting and a few more if there is device
> specific code needed for a specific card.
>
> Making console rely on a permanent daemon that is subject to getting
> killed by the OOM mechanism is not a workable solution.
Well, you keep forgetting that temporary programs are _also_ subject
to OOM, and that -- in case of problems -- exec() is less likely to
work than most other things.
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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
