Re: netatm: plan for removal unless an active maintainer is found

In message: <20060315185803.1956114c@xxxxxxxxxxxxxxxxxxxxxx>
Alexander Leidinger <Alexander@xxxxxxxxxxxxx> writes:
: Am Wed, 15 Mar 2006 10:29:03 -0700 (MST)
: schrieb "M. Warner Losh" <imp@xxxxxxxxxx>:
:
: > : > now available to work on the capi integration, and hopefully will do
: > : > the SMP safety work as part of that. If not, it's also on the
: > : > chopping block. It's a significant piece of otherwise unmaintained
: > : > code, and something that's not trivially testable (at least, not by
: > : > me or anyone I've talked to lately :-). I don't want to see it leave
: > : > the tree, but it needs to be updated so that it can run MPSAFE before
: > : > 7.0.
: > :
: > : I may add, that Hans-Petter Selasky has a MPSAFE replacement (written from
: > : scratch it seems) for I4B (AFAIK including capi) and the USB stack. I have
: > : tested or reviewed neither of them, but as far as I can read in the
: > : mailinglists, he adresses not only the issues you mention here, but he also
: > : provides bugfixes and additional features compared to our current code base.
: >
: > The problem is that this code isn't busdma safe at the moment. It was
: > posted for review on the NetBSD lists and this was the biggest set of
: > comments on tech-kern@xxxxxxxxxxx Since it isn't busdma safe, we'd
: > lose usb on sparc64 (and maybe arm) when this code is brought into the
: > tree. There have also been signficant concerns about the locking
: > that's done in the code as well, but I've not reviewed it recently.
: >
: > There's been a lot of work done here, and that work is generally good,
: > but last time I looked at the code it wasn't ready to be integrated to
: > the tree.
:
: The questions are:
: - What's less work to do?
: - Is there someone who is willing to do the work?

Agreed. Hans-Petter's work has great potential, but I think someone
with a lot of time and knowledge of FreeBSD specific issues is going
to need to work with him to properly integrate it into the tree. It
isn't a drop in right now, but could be with some work.

If usb abd usbHPS can co-exist in the tree, we might be able to do
some of this in-tree. But usb is a very important subsystem and
transitioning to a new code base is a high-risk thing.

Warner
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: CONFIG_OPTIMIZE_INLINING
    ... I'm giving up for the moment trying to review anything. ... only paid concern is Linux userland and so following Linux Kernel is a hobby. ... If you, Ingo, are going to push patches in before they can be reviewed, what ... Linus' tree or patches on there way to Linus' tree, ...
    (Linux-Kernel)
  • Re: netatm: plan for removal unless an active maintainer is found
    ... :> the tree, but it needs to be updated so that it can run MPSAFE before ... posted for review on the NetBSD lists and this was the biggest set of ... The computer revolution is over. ...
    (freebsd-arch)
  • Re: drag and drop in tree view was the single most redeeming featu
    ... Beta one didn't have drag and drop working... ... So "tree view is gone" I totally agree with, ... CNet's review is valid. ... pain is when you have files and go to find album info. ...
    (microsoft.public.windowsmedia)
  • Re: Can I cut the branches of my neighbors trees?
    ... The tree guy is going to send the bill to you, ... Or neighbors. ... Maybe you might like to review the thread before you feel qualified ...
    (alt.home.repair)