LWN: Comments on "Merge window opens, kgdb merged" https://lwn.net/Articles/278678/ This is a special feed containing comments posted to the individual LWN article titled "Merge window opens, kgdb merged". en-us Mon, 01 Sep 2025 10:10:36 +0000 Mon, 01 Sep 2025 10:10:36 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Big shared-memory x86 machines https://lwn.net/Articles/279043/ https://lwn.net/Articles/279043/ knan <div class="FormattedComment"><pre> There are development going on inside SGI for future and one-off machines, you know. The patch came from a SGI employee, and definitely is for x86-64. While their current big boxes are IA64, future machines doesn't need to be... </pre></div> Tue, 22 Apr 2008 12:46:41 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278812/ https://lwn.net/Articles/278812/ nowster <div class="FormattedComment"><pre> The latest git updates (post 2.6.25) fix ath5k's symbol problems. </pre></div> Sun, 20 Apr 2008 20:34:38 +0000 Big shared-memory x86 machines https://lwn.net/Articles/278780/ https://lwn.net/Articles/278780/ joib <div class="FormattedComment"><pre> That's correct, Altix ICE (and Altix XE) are clusters. Each 2-socket node runs its own kernel, and there is no shared memory between nodes, so inter-node communication is with message passing (MPI). AFAIK all big shared-memory machines SGI makes are Itanium-based. I suspect the answer to this conundrum is that this changeset just increases some previous x86-only max-cpu limit, and the mention of 4096-way machines refers to the Itanium-based SGI Altix. </pre></div> Sun, 20 Apr 2008 08:48:45 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278778/ https://lwn.net/Articles/278778/ trey <div class="FormattedComment"><pre> Not a single system image (SSI). Imho runs multiple instances of Linux kernel. </pre></div> Sun, 20 Apr 2008 07:59:42 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278772/ https://lwn.net/Articles/278772/ Cato <div class="FormattedComment"><pre> SGI systems include x86 versions with this CPU count - for example, NASA recently bought an Altix ICE blade server with 4096 Xeon CPUs: <a href="http://www.sgi.com/company_info/newsroom/press_releases/2007/september/nasa.html">http://www.sgi.com/company_info/newsroom/press_releases/2...</a> However, the line between this blade-based system and traditional Altix systems is not entirely clear, though presumably with the right problem a blade server would be just as good. </pre></div> Sun, 20 Apr 2008 06:23:43 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278769/ https://lwn.net/Articles/278769/ rsidd <div class="FormattedComment"><pre> As far as I know, SGI Altix is based on Itanium, not x86. I haven't come across an x86 machine with more than 32 processor cores (8 socket, 4 core Barcelona). </pre></div> Sun, 20 Apr 2008 01:37:08 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278762/ https://lwn.net/Articles/278762/ adobriyan > Doesn't this mean that the error/kloc figure is a bit biased then? <P> What errors are you talking about? <P> Nastygrams that even <TT>checkpatch.pl</TT> itself calls "WARNING"s? Sat, 19 Apr 2008 22:55:01 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278763/ https://lwn.net/Articles/278763/ linuxbox <div class="FormattedComment"><pre> The BSDs have their KGDB equivalent, and the self-contained DDB debugger as well. For Linux, the equivalent seems to be KDB. I'd enjoy seeing that cleaned up and merged. </pre></div> Sat, 19 Apr 2008 22:54:43 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278759/ https://lwn.net/Articles/278759/ sbergman27 <div class="FormattedComment"><pre> SGI Altix, I would think. A terabyte is a terabyte. Each processor can address any part of it. That's ram, of course. The architecture allows for 52 bits of virtual, or 4096 terabytes of that. There are, however, other difficulties to be overcome: <a href="http://lwn.net/Articles/229873/">http://lwn.net/Articles/229873/</a> </pre></div> Sat, 19 Apr 2008 22:54:01 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278758/ https://lwn.net/Articles/278758/ joib <div class="FormattedComment"><pre> As an aside, who makes 4096-way x86 machines (mentioned in the link about the x86 changes)? They must be pretty specialized machines, as with 40-bit physical addresses, which is what is found in current x86-64 cpu:s, they are limited to 1 TB total, or 250 MB/CPU. </pre></div> Sat, 19 Apr 2008 22:09:46 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278750/ https://lwn.net/Articles/278750/ rvfh <div class="FormattedComment"><pre> Thanks a lot :) Doesn't this mean that the error/kloc figure is a bit biased then? Although the conclusion remains the same: it decreased. Anyway, I do trust you clever people do the Right Thing, as the quality of my environment as a whole clearly shows. I just love Linux :) </pre></div> Sat, 19 Apr 2008 19:58:10 +0000 kmemcheck and ftrace https://lwn.net/Articles/278744/ https://lwn.net/Articles/278744/ Felix_the_Mac <div class="FormattedComment"><pre> It looks like some other useful stuff is there too. Am I right in thinking that the ftrace (latency tracer) patch has been merged? </pre></div> Sat, 19 Apr 2008 18:26:16 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278736/ https://lwn.net/Articles/278736/ mingo <div class="FormattedComment"><pre> the linecount jump in the code-quality table was because KVM was merged into the x86 tree under arch/x86/kvm/ and the lguest code was merged under arch/x86/lguest. also, we've got a new sub-architecture, more debug features such as kgdb, etc. etc. - each of which is extra code. Since v2.6.24-rc1 (which was the first big unification step with 600 unification patches) there were more than 1600 commits in arch/x86/. Every time we reduce size with a unification some new feature eats it up ;-) All in one: life didnt stop with unification :-) </pre></div> Sat, 19 Apr 2008 17:12:34 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278728/ https://lwn.net/Articles/278728/ rvfh <div class="FormattedComment"><pre> My thought exactly: I was expecting the merge to _reduce_ the code by, say, 20-30%... Any knowledgeable person care to explain? </pre></div> Sat, 19 Apr 2008 15:36:46 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278726/ https://lwn.net/Articles/278726/ muwlgr <div class="FormattedComment"><pre> It seems that x86 tree gets bloated (look at 117-&gt;136 KLOC step). Where are those famous code removers, so praised in LWN articles ? Would be great if they get their hands at the issue ... :&gt; </pre></div> Sat, 19 Apr 2008 15:20:21 +0000 Linus and kernel debugger at lca2008 https://lwn.net/Articles/278718/ https://lwn.net/Articles/278718/ willy <div class="FormattedComment"><pre> Ice cream for everybody! </pre></div> Sat, 19 Apr 2008 13:28:43 +0000 Linus and kernel debugger at lca2008 https://lwn.net/Articles/278696/ https://lwn.net/Articles/278696/ gdt <p>At the kernel miniconf at linux.conf.au Linus poked his head through the door just as debuggers were being discussed. After some "naughty schoolboys being discovered by the teacher" laughter over the coincidence of the timing it was plain that an elegant debugger patch might be accepted, and that some of the attendees were determined to create such a patch. It was also plain that Linus wasn't convinced about a debugger's usefulness in creating good code, but accepted that many people whom he respects were convinced.</p> Sat, 19 Apr 2008 04:41:15 +0000 Merge window opens, kgdb merged https://lwn.net/Articles/278684/ https://lwn.net/Articles/278684/ intgr <div class="FormattedComment"><pre> Wow, looks like the hell did freeze over! </pre></div> Fri, 18 Apr 2008 23:38:51 +0000