[мебелиBtrfs](http://btrfs.wiki.kernel.org/index.php/Main_Page) is new file system being developed. GPL licensed, this is what the page notes:

From a top screen output … on my laptop: top - 18:43:01 up 1:06, 2 users, load average: 1.19, 1.36, 1.17 Tasks: 178 total, 3 running, 175 sleeping, 0 stopped, 0 zombie Cpu0 : 11.9%us, 3.0%sy, 0.0%ni, 84.2%id, 0.0%wa, 1.0%hi, 0.0%si, 0.0%st Cpu1 : 76.2%us, 5.0%sy, 0.0%ni, 17.8%id, 0.0%wa, 0.0%hi, 1.0%si, 0.0%st Mem: 2571704k total, 1640064k used, 931640k free, 36796k buffers Swap: 995988k total, 0k used, 995988k free, 476952k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 7367 landman 20 0 1374m 541m 39m S 57 21.

John West at InsideHPC asks about 10 GbE on clusters. The point I made (in two posts), and we verify every time we spec a system out for a customer, is that 10 GbE is still priced higher per port than IB. This doesn’t mean we don’t like 10GbE. On the contrary, it is simpler/easier to deal with. But it comes at a price penalty, and a non-trivial one at that.

No, this is not the nswrapperplugin thunking layer thing that lets you run 32 bit NSAPI plugins on 64 bit linux. While that is a neat tool, it was prone to lots of crashing. No, this is an adobe native implementation of flash. I don’t have to kill npviewer.bin after/during firefox anymore. I don’t have to see large greyed out boxes when npviewer.bin crashes. This is good. Flash now works right … only took adobe 3 years after getting flash on Linux to get 64 bit basically right.

Ok, this is somewhat business related, I want to have a sense of what it is would make the most sense for you to have. For example, there are nice CUBLAS libs now. And some FFT implementations. What else do people need? Are you adopting an accelerator platform because the tools you need are there? Or are you resisting adopting the platform because of missing tools? What platforms are you looking at adopting and why?

Went in for my root canal today. Took them 7 X-tips to numb me up. Last week they tried preping the area and 10 didn’t do it (and that is the limit). Turns out they didn’t hit the right spot. They had to drill deep to get it. For those who don’t know, X-tip is wonderful. Though it hurts for 2-3 seconds as they drill and start depositing the anesthetic. That and it leaves an awful taste.

/. has a link to a Microsoft RIF rumor. And I heard from a number of sources about a big blue RIF. I have heard from a number of sources of rumors at Dell and others. AMD lost quite a few, including the father of the stream benchmark. There are likely others out there I haven’t covered/mentioned.

Ok … I had gone off on the OFED build/installation scripts for v1.3 and before, noting that it required that I do lots of patching, as the build environment … basically wrappers around rpmbuild, made distro specific assumptions. I don’t have a problem with using rpmbuild. RPMs annoy me in general, as they have been little more than a moving target, and sadly rendered effectively incompatible across distros. Not just the binary ones, but the source RPMs are very hard to build on any but the target distro.

Saw this mentioned all over the web … Quite a few of them are good. I like the “not so much” phrase though … sad to see it in need of banning. I liked the carbon footprint explanation. What a business model … heh … Ok. What words should we ban in HPC? Back when I was at SGI, we used to make fun of the marketeers with their “breakthrough”. Hence, I nominate “breakthrough”.

(for my fortran bretheren, != -> .ne. ) On /. is an object lesson in what not to do for valuable data. Backups are important. This cannot be stressed enough. More to the point, there are many things that are not backups. Snapshots come to mind. Yet we see people use them in this manner. In this day and age with “dedup” the fad d’jour (all it does is make each block that much more valuable, and important not to have go away …) backup is ever more important.