From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Convert btrfs software code to ASIC
Date: Mon, 19 May 2014 13:06:11 +0000 (UTC) [thread overview]
Message-ID: <pan$baa26$f0b99545$2d209bf8$14063927@cox.net> (raw)
In-Reply-To: B7F2379062E32745A8651FBDB20F64592FCF3D03@Server.waterlogic.com.au
Paul Jones posted on Mon, 19 May 2014 12:24:53 +0000 as excerpted:
>> On Mon, May 19, 2014 at 3:40 PM, Le Nguyen Tran <lntran.de@gmail.com>
>> wrote:
>>>
>>> I have a plan to develop an IC controller for Network Attached
>>> Storage (NAS). The main idea is converting software code into
>>> hardware implementation.
>>>
>>> I plan to use btrfs as the file system specification for my NAS.
> Perhaps a better idea would be to use a low-cost low-power som module
> to run Linux and btrfs code, and use an FPGA/ASIC to offload
> compression/encryption/checksums and to possibly act as a raid
> controller. Since btrfs will be under heavy development for the
> foreseeable future I doubt it would be a good idea to lock it into
> silicon. Using this approach the mature technologies can be hardware
> accelerated, and the software parts are available for easy upgrades.
> It also significantly reduces risk for your project, and VCs like that
> sort of thing!
This is a very good idea and what I was about to suggest. Certainly,
btrfs is still not fully stable, and I really would hate to see the
current implementation etched in silicon at this time. However, a hybrid
approach where the mature bits such as (de-/)compression/checksums/
encryption are hardware etched/accelerated while the more general and
still developing code is deployed as upgradeable firmware on a system-on-
module sounds like a very good idea indeed, particularly if that firmware
is deployed as a user-modifiable/replaceable free-as-in-freedom kernel in
keeping with the spirit of the GPL under which the Linux kernel and thus
btrfs are written.
In other words... I doubt very much that any list regular here familiar
with the continuing flow of bugs we see, as well as the roadmapped but
not yet implemented features that people wanting a hardware
implementation would certainly be interested in, would find the idea of a
hardware implementation of anything like current code anything but
nightmare material. =:^\ Maybe in a couple years... but even then,
upgradeable firmware with critical mature bits offloaded for hardware
acceleration sounds like a far better idea.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-05-19 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 8:40 Convert btrfs software code to ASIC Le Nguyen Tran
2014-05-19 10:41 ` Fajar A. Nugraha
2014-05-19 11:07 ` Le Nguyen Tran
2014-05-19 12:24 ` Paul Jones
2014-05-19 13:06 ` Duncan [this message]
2014-05-19 13:09 ` Le Nguyen Tran
2014-05-19 13:53 ` Fajar A. Nugraha
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='pan$baa26$f0b99545$2d209bf8$14063927@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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).