From: Ralf Baechle DO1GRB (qfux@itsusnow.com)
Date: Tue Aug 06 2002 - 13:22:39 EEST
On Mon, Aug 05, 2002 at 08:35:20PM +0100, M Taylor wrote:
> > and 2.2 kernels (I have yet to get it to run for >24 hours on a 2.4
> > kernel without a kernel panic, with my Baycom scc card and all my other
> > ports). Yes, it nominally sends some packets around. No, it doesn't do
> > it correctly.
>
> Do you have an decoded Oops from a 2.4 kernel panic?
I'd also interested just to see it the AX.25 stack or any of the ham radio
drivers was the culprit.
> I disagree with the idea of putting the AX.25 (and/or Net/ROM) network
> protocol stacks into userspace. That would be a silly idea with no
> benefit.
I'm not sure if we already can put a full network stack into userspace
while maintaining the socket API. And anything but the standard socket
API is inacceptable. In particular I consider apps that come with their
own stack builtin like TheNetNode heavily missdesigned.
> The idea of putting amateur radio device drivers (mkiss, BayCom, soundcard,
> SCC, etc.) in userspace only makes sense for soundcard and perhaps BayCom,
> because of the amount of CPU utilitization by these drivers. Since I don't
> use BayCom I am not certain, but it may or may not use enough CPU to
> make it sensible to put it into userspace. I suspect userspace soundcard
> is safer. Why would you want mkiss, SCC or other drivers in userspace?
Soundmodem is doing heavy numbercrunching. That's a workload that doesn't
behave to nicely in there kernel where the driver cannot be preempted. Once
the 2.5 scheduler redesign finally has finished I hope running a realtime
workload like soundmodem in userspace will be reliable.
73 de DO1GRB op Ralf
-- Loc. JN47BS / CQ 14 / ITU 28 / DOK A21 - To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to fconaao.yuckcetseg@iesg.com More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Tue Aug 06 2002 - 14:53:05 EEST