From: Christian Stroetmann <stroetmann@ontolinux.com>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Tux3 Report: Meet Shardmap, the designated successor of HTree
Date: Wed, 19 Jun 2013 20:17:12 +0200 [thread overview]
Message-ID: <51C1F5A8.2080303@ontolinux.com> (raw)
In-Reply-To: <1EC23D2B9975384993D85B5DB93AAE8860D35B@sisaex02sj>
Aloha everybody
We would like to thank the developers very much for giving technical
details about how we could implement our file system indexing (see [1]
and [2]).
[1] SASOS4Fun (www.ontonics.com/innovation/pipeline.htm#sasos4fun) Do
not confuse SIP with SipHash, but put SipHash in relation with "the size
of [a] hash table [is determined] by sampling the input", as we
understood the description.
[2] Ontonics, OntoLab, and OntoLinux Further steps
(www.ontomax.com/newsarchive/2012/october.htm#08.October.2012)
Sincerely
Christian Stroetmann
next prev parent reply other threads:[~2013-06-19 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 2:31 Tux3 Report: Meet Shardmap, the designated successor of HTree Daniel Phillips
2013-06-19 18:17 ` Christian Stroetmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-20 17:02 Daniel Phillips
2013-06-20 19:11 ` Christian Stroetmann
2013-06-20 20:27 ` Daniel Phillips
2015-04-15 18:00 ` Christian Stroetmann
2013-06-24 14:18 ` Pavel Machek
2013-06-24 15:16 ` Christian Stroetmann
2013-06-24 15:39 ` Andreas Karlsson
2013-06-24 17:19 ` Christian Stroetmann
2013-06-24 18:20 ` richard -rw- weinberger
2013-06-25 0:34 ` Christian Stroetmann
2013-06-25 0:15 ` David Lang
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=51C1F5A8.2080303@ontolinux.com \
--to=stroetmann@ontolinux.com \
--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).