I've been through Narita airport several times but, sadly, never stayed in Japan so this trip was a real treat and I thoroughly enjoyed Yokohama and this event. The web site for this event can be seen here - http://events.linuxfoundation.org/events/linuxcon-japan.
All of the talks were videod and will be on line at some point. It is the third of these events and drew a good technical crowd, but perhaps that was due more to having Linus Torvalds there than me. It was also good to be able to offer some support, however small, to Japan following the terrible events of March 11th.
Linus surprised the world by announcing v3.0 and he explained this during his Q&A session as being the right time, it being 20 years of Linux and 2.6 having been around a very long time, essentially since they moved to an always stable development flow. He also said some kind words about the ARM Linux community and welcomed the group maintained ARM subarchitecture maintainance tree in kernel.org that we are setting up. The picture above is the first that we've had together since the Digital Alpha days about 19 years ago. For various reasons, this was after drinking some good Japanese whisky.
One of the ongoing discussions was about how we could support the more traditional embedded Linux world with long term supported kernel versions. The idea is that we would pick one a year and back port useful bug fixes etc into it. The situation at the moment appears to be that each company is already doing this, so maybe doing it together would reduce the burden and create a better result. The tricky bit would be to get the users of such a tree to agree on the version, in particular the distributions. I think that this is where standards organisations, such as Genivi would fit. An interesting idea though and one that I will raise in Linaro.
There was also a good technical talk from Ted T'so talking about performance of EXT4 on SMP systems. Basically, too many locks does not help performance, but it also really shows that in order to understand and tune such systems, you really need instrumentation and good benchmarks.