On Sun, 2009-11-29 at 09:49 -0800, Ray Lee wrote: > On Sun, Nov 29, 2009 at 9:28 AM, Maxim Levitsky <maximlevitsky@xxxxxxxxx> wrote: > > This has zero advantages besides good developer feeling that "My system > > has one less daemon..." > > Surely it's clear that having an unnecessary daemon is introducing > another point of failure? A failure in a userspace IR daemon is worst case loss of IR functionality. A failure in kernel space can oops or panic the machine. > Reducing complexity is not just its own > reward in a 'Developer Feel Good' way. No complexity is being reduced here. It's being shoved from one side of a fence to another. A bad part about the proposed move is that in user space, user address space is fairly isolated from other applications and separate from kernel space. Partitioning reduces complexity and the impact of failures. Moving things into kernel space just adds more to the pile of code; it should have a good reason for being there. > If decoding can *only* be sanely handled in user-space, that's one > thing. If it can be handled in kernel, then that would be better. Why does the address space in which decoding is performed make the decoding process better or worse? The in kernel infrastructre and restrictions add constraints to a decoding implementation. Userspace is much more flexible. Regards, Andy -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
