"I'm a bit behind after investigating the TCP performance issues that turned out to be HW specific problems. It's a bit of a disappointment, I thought maybe there was a cool bug to fix in TCP :-)" explained David Miller, posting his networking merge plans for the upcoming 2.6.24 kernel. He noted, "I merged in Jeff Garzik's and John Linville's latest and I'm running the current tree on my workstation most of today with good results so far." David added, "I plan to commit my Neptune driver in it's current state, and that's the last new feature going in."
In an earlier discussion last month on the Linux netdev mailing list, David described how many changes were in his net-2.6.24 git tree, "it's to the point where every single bug fix put into Linus's tree creates a merge conflict with net-2.6.24, we are simply touching that much stuff. :-)" He added, "we've touched so much in net-2.6.24 that we really should be auditing the thing and fixing any bugs that have been added. If you're bored and looking for something to do, pick an odd NAPI driver and audit it in the net-2.6.24 tree."
From: David Miller
Subject: net-2.6.24 plans
Date: Oct 3, 2:36 am 2007
I'm a bit behind after investigating the TCP performance issues that
turned out to be HW specific problems. It's a bit of a
dissapointment, I thought maybe there was a cool bug to fix in TCP :-)
Anyways, that means there are patches backlogged in my inbox and it is
also about time to do the hopefully last rebase of the net-2.6.24
tree.
I merged in Jeff Garzik's and John Linville's latest and I'm running
the current tree on my workstation most of today with good results so
far.
Linus should release the final 2.6.23 very soon, let's kind of assume
it will happen over the next 3 or 4 days.
That means we need to bear down for the merge. I plan to commit my
Neptune driver in it's current state, and that's the last new feature
going in.
You can help make the merge go swimmingly by picking some nagging
issue you noticed and track it down. If you can figure out why
something happens but can't or don't have time to come up with
a fix, report what you've discovered.
If you can provide the fix too, all the better.
That's how I get backlogged, I'm working on A and notice some problem
with B, then I refuse to go back to A until I bring closure to B. :)
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: David Miller
Subject: net-2.6.24 plans
Date: Sep 16, 8:22 pm 2007
Most if not all of my 2 week backlog of patches is in the net-2.6.24
and net-2.6 tree now. And any relevant -stable fixes will be
submitted in the next day or two.
Tomorrow (Monday) I want to rebase the net-2.6.24 tree one more time
to deal with all of the conflicts which exist between
linux-2.6/net-2.6 and net-2.6.24, but I'll likely defer that
until the net-2.6 fixes I just pushed to Linus are integrated.
It's to the point where every single bug fix put into Linus's tree
creates a merge conflict with net-2.6.24, we are simply touching that
much stuff. :-)
I expect some small network namespace fixes from Eric B., but that's
basically it as far as 2.6.24 is concerned. Oh yes, there are also
the MAC_FMT/MAC_ARG bits from Joe Perches that I need to do a merge
of.
The transmit batching stuff needs a lot more analysis and discussion,
so I definitely see that stuff as 2.6.25 material. I think if we can
avoid a food fight between Jamal and Mr. Kumar and have healthy
discussions, we can end up with a really nice implementation. So
everyone put your boxing gloves away and let's get at it. :-)
We've touched so much in net-2.6.24 that we really should be auditing
the thing and fixing any bugs that have been added. If you're bored
and looking for something to do, pick an odd NAPI driver and audit it
in the net-2.6.24 tree.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Whats new?
Whats new/changed in this networking update?
Any new features?
Support for anything new?
Anything fixed?
Anything improved?
See for yourself.
just read the changelog . it's not that hard.
http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.24.git;a=summary