From: Daniel Phillips <phillips@phunq.net>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, tux3@tux3.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Tux3 Report: Tux3 Debut at SCALE 7x
Date: Mon, 23 Feb 2009 05:00:35 -0800 [thread overview]
Message-ID: <200902230500.36275.phillips@phunq.net> (raw)
On Sunday, Tux3 was presented at SCALE 7x in Los Angeles:
http://scale7x.socallinuxexpo.org/
Slides from the presentation are here:
http://tux3.org/docs/tux3.scale.7x.pdf
Audio will be available later (eek!).
The presentation was given on a ten year old Vaio laptop running
a completely modern Debian Sid, with XFCE, Openoffice, and one of
Linus's latest kernels from Git. The root filesytem was Tux3:
http://tux3.org/images/tux3.root.jpg
Preliminary benchmarks show Tux3 performing well, though optimization
work has not yet begun in earnest. Many thanks to the usual cast of
characters, especially Hirofumi who continued to feed me bug fix
patches into the wee hours of Sunday morning, and Timothy Huber who
provided a wild ride to the show as well as some very slick graphics.
Tux3 did not crash. That is good, because recovery is not fully
implemented. However, we think it is about time to start reviewing
this code, with a view to getting an early merge. The essential
structure is all there, and it works pretty well. Tux3 has plenty to
offer in terms of advancing the state of the art of Linux storage,
and will best be able to offer that as part of mainline.
Tux3 source code is here:
http://hg.tux3.org/tux3
http://hg.tux3.org/tux3/file/3118107954f1/user/kernel/
A Git tree will appear soon, along with proper kernel patches. But
that is for later and now is time to sleep. It has been a long week.
Regards,
Daniel
reply other threads:[~2009-02-23 13:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200902230500.36275.phillips@phunq.net \
--to=phillips@phunq.net \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tux3@tux3.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®