linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Le Nguyen Tran <lntran.de@gmail.com>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Convert btrfs software code to ASIC
Date: Mon, 19 May 2014 13:07:19 +0200	[thread overview]
Message-ID: <CAF_AmaOJF4W5uABSvrtBGg7NUzcmE03Qtom+THKFEP_oYH3gmg@mail.gmail.com> (raw)
In-Reply-To: <CAG1y0sf9tW+151DMvihWgRFnbUs3Q=uKyL3W4_heU7rYBQz0=w@mail.gmail.com>

Hi Nugraha,

Thank you so much for your information. Frankly speaking, no one can
confirm a new start-up idea works or not. The probability of failure
is always high. However, the benefit if it works is also very high.

I do not plan to exactly replicate the C source code. There are always
some techniques in ASIC design to implement which are not the same as
in software (less flexible but faster).

The main advantages of my proposed chip are:
- Very high performance: Performance of ASIC chip is normally more
than 10x higher than performance of processors because processor run
only 1-4 instructions sequentially. That is very suitable for server
when there are many requests from users.
- Low-cost: In side the chip, we can customized for our function only.
In my plan, we do not need cache (which covers a very large area), and
we can use low cost technology 0.18um.
- Low-power: Processors run instructions sequentially and access
memory ( or cache). As a result, they consume much more power than
ASIC chip (also can be 10x higher).

Actually ARM processors like mediatek cannot be comparable with ASIC
chip. However, as I mentioned, it is just my draft idea. I still to
work more to verify my idea.

Thanks.

Nguyen.

On 5/19/14, Fajar A. Nugraha <list@fajar.net> wrote:
> On Mon, May 19, 2014 at 3:40 PM, Le Nguyen Tran <lntran.de@gmail.com>
> wrote:
>> Hi,
>>
>> I am Nguyen. I am not a software development engineer but an IC (chip)
>> development engineer. I have a plan to develop an IC controller for
>> Network Attached Storage (NAS). The main idea is converting software
>> code into hardware implementation. Because the chip is customized for
>> NAS, its performance is high, and its cost is lower than using micro
>> processor like Atom or Xeon (for servers).
>>
>> I plan to use btrfs as the file system specification for my NAS. The
>> main point is that I need to understand the btrfs sofware code in
>> order to covert them into hardware implementation. I am wandering if
>> any of you can help me. If we can make the chip in a good shape, we
>> can start up a company and have our own business.
>
> I'm not sure if that's a good idea.
>
> AFAIK btrfs depends a lot on other linux subsystems (e.g. vfs, block,
> etc). Rather than converting/reimplementing everything, if your aim is
> lower cost, you might have easier time using something like a mediatek
> SOC (the ones used on smartphones) and run a custom-built linux with
> btrfs support on it.
>
> For documentation,
> https://btrfs.wiki.kernel.org/index.php/Main_Page#Developer_documentation
> is probably the best place to start
>
> --
> Fajar
>

  reply	other threads:[~2014-05-19 11:07 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 [this message]
2014-05-19 12:24     ` Paul Jones
2014-05-19 13:06       ` Duncan
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=CAF_AmaOJF4W5uABSvrtBGg7NUzcmE03Qtom+THKFEP_oYH3gmg@mail.gmail.com \
    --to=lntran.de@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=list@fajar.net \
    /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).