From: Ralf Baechle DO1GRB <ralf@linux-mips.org>
To: M Taylor <mctylr@privacy.nb.ca>
Cc: linux-hams@vger.kernel.org
Subject: Re: AX.25 in kernel 2.5 status?
Date: Thu, 10 Oct 2002 19:22:28 +0200 [thread overview]
Message-ID: <20021010192228.A565@linux-mips.org> (raw)
In-Reply-To: <20021010035703.B8136@pull.privacy.nb.ca>; from mctylr@privacy.nb.ca on Thu, Oct 10, 2002 at 03:57:03AM +0100
On Thu, Oct 10, 2002 at 03:57:03AM +0100, M Taylor wrote:
> A while back (a few months ago) a couple of developers/hams (Ralf and others)
> mentioned that work needed to be done in the 2.5 linux kernel due to changes
> (I believe relating cli()/sti() plus other things).
>
> Has there been any progress? There appears to be some patches included
> in 2.5.37 from Ralf and David Miller. Does include all the changes we
> _need_ to make? (that is for when cli()/sti() and such calls go away)
Not by far. The entire locking in the code is a mess. It just happens
to work if you're nice to the code that is uniprocessor, no preemption
patches, avoid configuring routes etc. while the system is active etc.
Fixing all those omissions takes a while. And cli/sti was just the peak
of the ice berg. The SOCKCALL_WRAP wrap stuff will go away for example
and getting away without that require even more auverhaul of the locking
strategy which I'm just working on.
The result will probably be the only multithreaded AX.25, NETROM and ROSE
stacks on the planet. An attribute of dubious value for a low bandwidth
protocols - but at least the thing will work.
> I guess I am asking what needs to be done before users can "safely" use
> 2.5.x kernels for amateur radio stuff.
2.4 needs the same stuff. If it's working for you then just because you're
not shaking the code hard enough.
> Should the http://sourceforge.net/projects/ax25 Bug tracking, Support
> Requests / Patches / Feature Requires be used for the AX.25 (et all)
> kernel as well as the userland libraries, tools, and apps?
That project looks rather dead.
Anyway, all the userspace stuff stays usable. I've been careful to not
change any of the kernel interfaces.
> Oh, and can a non-kernel programmer help? (I'm not familiar with kernel
> programming, but I can program, can I be of assistance?)
I don't have the bandwidth to do that but I think we need some documentation
of the AX.25 / NETROM/ ROSE network interface for programmers. And all
the userspace stuff is still way too complex for the average "plug and play"
ham ...
Ralf
next prev parent reply other threads:[~2002-10-10 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 2:57 AX.25 in kernel 2.5 status? M Taylor
2002-10-10 17:22 ` Ralf Baechle DO1GRB [this message]
2002-10-11 9:49 ` Steven Whitehouse
2002-10-11 13:03 ` Ralf Baechle DO1GRB
2002-10-11 13:47 ` Steven Whitehouse
2002-10-11 14:35 ` Ralf Baechle DO1GRB
2002-10-11 14:56 ` Steven Whitehouse
2002-10-11 15:38 ` Ralf Baechle DO1GRB
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021010192228.A565@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-hams@vger.kernel.org \
--cc=mctylr@privacy.nb.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox