linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <daniel@phunq.net>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>, daye <daye@dddancer.com>
Subject: [ANNOUNCE] Three things.
Date: Thu, 29 Aug 2019 15:16:48 -0700	[thread overview]
Message-ID: <8ccfa9b4-d76c-b25d-7eda-303d8faa0b79@phunq.net> (raw)

Hi folks, how's it going? Over here, we have been rather busy lately,
and for the last five years or so to be honest. Today it is my pleasure
to be able to announce three GPL open source projects:

1) Shardmap

Shardmap is the next generation directory index developed for Tux3, and
which we are now offering as a much needed replacement for Ext4 HTree.
Shardmap meets but usually beats HTree at all scales, has way better
readdir characteristics, and goes where HTree never did: up into the
billions of files per directory, with ease. Shardmap also is well on
its way to becoming a full blown standalone KVS in user space with sub
microsecond ACID operations in persistent memory.[1]

Code for Shardmap is here:

    https://github.com/danielbot/Shardmap

2) Teamachine

Teamachine is a direct threaded code virtual machine with a cycle time
of .7 nanoseconds, which may just make it the fastest interpreter in the
known universe. Teamachine embeds Shardmap as a set of micro ops. With
Teamachine you can rapidly set up a set of Shardmap unit tests, or you
can build a world-beating query engine. Or just kick back and script
your game engine, the possibilities are endless.

Code for Teamachine is here:

    https://github.com/danielbot/TeaMachine

3) Tux3

Tux3 is still alive, is still maintained against current mainline, and
is still faster, lighter, and more ACID than any other general purpose
Linux file system. Inasmuch as other devs have discovered that the same
issue cited as the blocker for merging Tux3 (get user pages) is also
problematic for kernel code that is already merged, I propose today that
we merge Tux3 without further ado, so that we can proceed to develop
a good solution together as is right, proper and just.

Code for Tux3 is here:

    https://github.com/OGAWAHirofumi/tux3/tree/hirofumi

Everyone is welcome to join OFTC #tux3 and/or post to:

   http://tux3.org/cgi-bin/mailman/listinfo/tux3

to discuss these things, or anything at all. Fun times. See you there!

STANDARD DISCLAIMER: SHARDMAP WILL EAT YOUR DATA[2] TEAMACHINE WILL HALT
YOUR MACHINE AND SET IT ON FIRE. DOWNLOAD AND RUN OF YOUR OWN FREE WILL.

[1] Big shoutout to Yahoo! Japan for supporting Shardmap work.

[2] Tux3 is actually pretty good about not eating your data, but that is
another thing.

NB: followup posts are in the works re the detailed nature and status of
Shardmap, Teamachine and Tux3.

Regards,

Daniel

             reply	other threads:[~2019-08-29 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 22:16 Daniel Phillips [this message]
2019-09-02 15:10 ` [ANNOUNCE] Three things OGAWA Hirofumi

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=8ccfa9b4-d76c-b25d-7eda-303d8faa0b79@phunq.net \
    --to=daniel@phunq.net \
    --cc=daye@dddancer.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).