"It's two weeks (and one day), and the merge window is over," began Linus Torvalds, announcing the 2.6.27-rc1 kernel. He continued, "finally. I don't know why, but this one really did feel pretty dang busy. And the size of the -rc1 patch bears that out - at 12MB, it's about 50% bigger than 26-rc1 (but not that much bigger than 24/25-rc1, so it's not like it's anything unheard of)." He reflected, "the pure size of the -rc's _is_ making me a bit nervous, though. Sure, it means that we are good at merging it all, but I have to say that I sometimes wonder if we don't merge too much in one go, and even our current (fairly short) release cycle is actually too big." As for the actual changes, Linus explained:
"Much of -rc1 was in linux-next, but certainly not everything. We'll see how that whole thing ends up evolving - it certainly didn't solve all problems, and there was some bickering about things that weren't there (and some things that mostly were ;), but maybe it helped. There's a ton of new stuff in there, but at least personally the interesting things are the BKL pushdown and perhaps the introduction of the lockless get_user_pages_fast(). The build system also got updated to allow moving the architecture include files ('include/asm-xyz') into the architecture subdirectories ('arch/xyz/include/asm'), and sparc seems to have taken advantage of that already."
Other changes Linus highlighted included merging the UBI filesystem, as well as, "tracing, firmware loading, continued x86 arch merging, and moving more code to generic support (unified generic IPI handling, coherent dma memory allocation, show_mem etc). Bootmem rewrites. [And] some support for further scalability (ie 4k cpu cores)."
From: Linus Torvalds <torvalds@...>
Subject: Linux v2.6.27-rc1
Date: Jul 28, 11:23 pm 2008
It's two weeks (and one day), and the merge window is over.
Finally. I don't know why, but this one really did feel pretty dang busy.
And the size of the -rc1 patch bears that out - at 12MB, it's about 50%
bigger than 26-rc1 (but not that much bigger than 24/25-rc1, so it's not
like it's anything unheard of).
The pure size of the -rc's _is_ making me a bit nervous, though. Sure, it
means that we are good at merging it all, but I have to say that I
sometimes wonder if we don't merge too much in one go, and even our
current (fairly short) release cycle is actually too big.
Anyway, that's a discussion for some other event.
Much of -rc1 was in linux-next, but certainly not everything. We'll see
how that whole thing ends up evolving - it certainly didn't solve all
problems, and there was some bickering about things that weren't there
(and some things that mostly were ;), but maybe it helped.
There's a ton of new stuff in there, but at least personally the
interesting things are the BKL pushdown and perhaps the introduction of
the lockless get_user_pages_fast(). The build system also got updated to
allow moving the architecture include files ("include/asm-xyz") into the
architecture subdirectories ("arch/xyz/include/asm"), and sparc seems to
have taken advantage of that already.
But those changes are just small details in the end. As usual, the bulk of
changes are all to device drivers (roughly half, as usual), with the arch
directory amounting to about half of the remainder. Dirstat:
3.2% arch/arm/
9.2% arch/ppc/
24.6% arch/
5.2% drivers/char/drm/
6.3% drivers/char/
4.5% drivers/gpu/drm/
4.5% drivers/gpu/
4.6% drivers/media/video/
5.5% drivers/media/
3.0% drivers/net/wireless/
10.7% drivers/net/
6.4% drivers/usb/misc/
4.7% drivers/usb/serial/
12.9% drivers/usb/
51.2% drivers/
4.4% firmware/
3.7% fs/
9.2% include/
where the bulk of that fs/ update is the merge of the UBI filesystem, to
pick one fairly sizeable chunk outside of arch or drivers (there's omfs
too, but that's tiny in comparison).
Other stuff? tracing. firmware loading. continued x86 arch merging. And
moving more code to generic support (unified generic IPI handling,
coherent dma memory allocation, show_mem etc). bootmem rewrites. Some
support for further scalability (ie 4k cpu cores).
But mostly lots and lots of driver and arch updates.
Go to kernelnewbies or lwn for more reporting, I'm going to sleep for
twenty-four hours now ;)
Linus
--
And what about....
And what about the famous and expected unified asynchronous I/O framework??
When can we expect?
Still not convinced about Linux quality
Andrew Morton from the last mail in the thread:
"But it's all shuffling deckchairs, really. Are we actually merging
better code as a reasult of all of this? Are we being more careful and
reviewing better and testing better?"
"Don't think so."
http://marc.info/?l=linux-kernel&m=121740867428873&w=2
Wow, the trolls are bored I guess...
LOL, what do these trolls hope to accomplish by posting their silly musings here? I read their comments and it's sad, yet funny. As if the doubts of some anonymous coward flamer count for anything...
Your comment was sad, but
Your comment was sad, but not funny.
Happy Troll Day.
If Andrew Morton is a troll
If Andrew Morton is a troll then I'm Santa.
more troll fun
Andrew Morton is not a troll, he is an actual person, and made a comment about a specific testing branch of code. The one who is the troll is the one who wanted us all to know that he's "still not convinced" about the quality of linux, quoting andrew morton out of context to try to make it appear that he was saying something bad about linux in general
LOL, the troll "is still not convinced" - as if anyone gives a crap about his doubts...
No one gives a crap about
No one gives a crap about yours.
apparently
apparently you do
hola viteh
hola viteh
Chasing windows
Well linux began to move on the way to chase windows innovation. As long as we support maybe someday it will beat windows