From: Daniel Phillips <daniel@phunq.net>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Subject: Re: [RFC] Thing 1: Shardmap fox Ext4
Date: Sun, 8 Dec 2019 02:25:22 -0800 [thread overview]
Message-ID: <3b4d380f-cb33-b0fb-2426-67109875ce77@phunq.net> (raw)
In-Reply-To: <20191128022817.GE22921@mit.edu>
On 2019-11-27 6:28 p.m., Theodore Y. Ts'o wrote:
> The use of C++ with templates is presumably one of the "less so"
> parts, and it was that which I had in mind when I said,
> "reimplementing from scratch".
The templates were removed without reimplementing from scratch:
https://github.com/danielbot/Shardmap/blob/master/shardmap.h#L88
https://github.com/danielbot/Shardmap/blob/master/shardmap.cc#L82
The duopack/tripack facility, central to Shardmap efficient scalability, are
now just ordinary C code that happens to be compiled by a C++ compiler. I
think the machine code should be identical to what the templates produced,
though I did not verify.
This was a strictly mechanical conversion, less error prone than
reimplementing from scratch I would think. I expect the rest of the
back conversions to be similarly mechanical.
Regards,
Daniel
next prev parent reply other threads:[~2019-12-08 10:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 1:47 [RFC] Thing 1: Shardmap fox Ext4 Daniel Phillips
2019-11-27 7:40 ` Vyacheslav Dubeyko
2019-11-27 8:28 ` Daniel Phillips
2019-11-27 19:35 ` Viacheslav Dubeyko
2019-11-28 2:54 ` Daniel Phillips
2019-11-28 9:15 ` Andreas Dilger
2019-11-28 10:03 ` Daniel Phillips
2019-11-27 14:25 ` Theodore Y. Ts'o
2019-11-27 22:27 ` Daniel Phillips
2019-11-28 2:28 ` Theodore Y. Ts'o
2019-11-28 4:27 ` Daniel Phillips
2019-11-30 17:50 ` Theodore Y. Ts'o
2019-12-01 8:21 ` Daniel Phillips
2019-12-04 18:31 ` Andreas Dilger
2019-12-04 21:44 ` Daniel Phillips
2019-12-05 0:36 ` Andreas Dilger
2019-12-05 2:27 ` [RFC] Thing 1: Shardmap for Ext4 Daniel Phillips
2019-12-04 23:41 ` [RFC] Thing 1: Shardmap fox Ext4 Theodore Y. Ts'o
2019-12-06 1:16 ` Dave Chinner
2019-12-06 5:09 ` [RFC] Thing 1: Shardmap for Ext4 Daniel Phillips
2019-12-08 22:42 ` Dave Chinner
2019-11-28 21:17 ` [RFC] Thing 1: Shardmap fox Ext4 Daniel Phillips
2019-12-08 10:25 ` Daniel Phillips [this message]
2019-12-02 1:45 ` Daniel Phillips
2019-12-04 15:55 ` Vyacheslav Dubeyko
2019-12-05 9:46 ` Daniel Phillips
2019-12-06 11:47 ` Vyacheslav Dubeyko
2019-12-07 0:46 ` [RFC] Thing 1: Shardmap for Ext4 Daniel Phillips
2019-12-04 18:03 ` [RFC] Thing 1: Shardmap fox Ext4 Andreas Dilger
2019-12-04 20:47 ` Daniel Phillips
2019-12-04 20:53 ` Daniel Phillips
2019-12-05 5:59 ` Daniel Phillips
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=3b4d380f-cb33-b0fb-2426-67109875ce77@phunq.net \
--to=daniel@phunq.net \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).