From c1cb54658465a70a1e8ae293c49869d759fa52cb Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Tue, 19 Jul 2011 22:50:12 +0200 Subject: news: qoth 2, PS: Hurd truths and rumors --- news/2011-q2-ps.mdwn | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 news/2011-q2-ps.mdwn diff --git a/news/2011-q2-ps.mdwn b/news/2011-q2-ps.mdwn new file mode 100644 index 00000000..62c2503f --- /dev/null +++ b/news/2011-q2-ps.mdwn @@ -0,0 +1,37 @@ +Hurd truths and rumors +====================== + +After [[our latest Quarter of the Hurd|news/2011-q2]] has been picked up by slashdot and phoronix did some [performance tests of the Hurd][phorperf], discussions have been running all over the net. While we are happy to see that there obviously is quite some interest in the Hurd, we also saw some rumors and outdated information flowing around. We hope that we will be able to clear them up a bit. + +[phorperf]: http://www.phoronix.com/scan.php?page=article&item=debian_gnu_hurd&num=1 + +* Debian wants to replace Linux with the Hurd: ✘ Wrong: We plan to get into Wheezy as an additional port besides Linux and kFreeBSD; but we don't know whether we will make it. It depends on a lot of factors, such as porting the DDE toolkit to inherit Linux 2.6 network card drivers, porting more packages, and finishing the existing support. If you want to help [[porting|contributing/porting]], please contact us: We need you! + +* Hurd developers want Linux to die: ✘ Wrong: All of us are happy Linux users, and GNU/Linux currently is the only free system you can actually give to nontechnical users (and make them happy with free software), so it is the most important tool for spreading free software. We don’t work on the Hurd because of some kind of hatred against Linux or Linus. We like and use Linux. We work on the Hurd, because of the [[additional possibilities and clean design|advantages]] it provides. + +* Java support on the Hurd is in the works. ✔ True: jkoenig is working on porting Java (OpenJDK 7) as part of his [[gsoc_project|user/jkoenig/java]]. This should help us towards better archive coverage. It must however also be said that Java support *already* exists on the Hurd, through the gcj/ecj platform. jkoenig is also fixing a few important things there. + +* The Hurd has no Xorg: ✘ Wrong: X.Org *does* work -- see [[instructions|unsorted/DebianXorg]] (Some drivers won't work anymore, though, as they require DRM nowadays). + +* The Hurd only runs on legacy hardware: ✘ Wrong: The Hurd is only tested a few platforms, but it likely runs on modern processors. If you want to see if it works for you, just test the [[LiveCD|hurd/running/live_cd]]. + +* Hurd only supports legacy devices: ½ Partly True: Currently most drivers are from Linux 2.0. For network cards, Linux 2.6+ drivers are available through DDE, though (needs manual setup for now). With a good amount of work, DDE also allows porting other classes of drivers to allow using the drivers from recent Linux releases — and push them into userspace. + +* The Hurd has no SMP: ✔ True: Even though the Hurd servers support SMP and GNU Mach has SMP support. But the latter [[does_not_yet_have_drivers_for_nowadays_chipsets|faq/smp]], so the Hurd currently can’t take advantage of multiple cores. + +* Developing a microkernel must be harder than developing a monolithic kernel, because the Hurd took so long. ✘ Wrong: For the last decade, the Hurd had on average 5 hobby developers. That these developers managed to get the Hurd into a state where it actually gets not too far from the Linux kernel in performance — which has about 1000 developers, many of them full time — shows the efficiency of the Hurd’s design. + +* The system is called GNU/GNU Hurd: ✘ Wrong: The GNU userland (glibc, coreutils, …) and the GNU Hurd together form the GNU system. To avoid being mistaken for GNU/Linux, we normally use the name GNU/Hurd or GNU Hurd. The *correct* name is simply GNU. + +Test results +------------ + +Quite good. We expected that the microkernel design of the Hurd would have a far more severe performance hit. + +Some explanations: + +* CPU bound. +* IPCs [are no more such a problem on recent hardware][ipc]. +* The emulation layer should rather make the context switches worse, so it’s likely not at play. + +[ipc]: http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.51.16 -- cgit v1.2.3