Ingo Molnar wrote:
* Christoph Hellwig <[email protected]> wrote:
Personally I think interrupt threads, spinlocks as sleeping mutexes
and PI is something we should keep out of the kernel tree. [...]
it's not really a problem - they integrate nicely. They also found
dozens of hard-to-catch bugs already so if you dont care about embedded
systems at all then worst-case you can consider it a spinlock debugging
mechanism, with the difference that DEBUG_SPINLOCK is far uglier ;)
Anyway, this discussion is premature, as i'm not submitting all these
patches yet.
Probably the concern is in multiplicative increase in complexity of
configurations and I'm sure the code itself is more complex too.
Of course this is weighed off against the improvements added to the
kernel. I'm personally not too clear on what those improvements are;
a bit better soft-realtime response? (I don't know) What kind of
userbase increase would that allow? .01%, 1.0%...? Is that large
enough to warrant being included in the kernel? Does it even make
technical sense to do this in the general purpose kernel rather than
a specialised solution?
Those are the kinds of questions that will have to be debated (I
guess this mail is directed more towards Daniel than you, Ingo :)).
Nick
-
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]
