1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
|
Return-Path: <alex@betarho.net>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id E5A46B13
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 13 Jul 2015 13:04:20 +0000 (UTC)
X-Greylist: delayed 00:09:03 by SQLgrey-1.7.6
Received: from jetson-mail (unknown [90.171.36.71])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 25463EA
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 13 Jul 2015 13:04:20 +0000 (UTC)
Received: from owncloud.betarho.net (owncloud.betarho.net [172.21.128.6])
by jetson-mail (Postfix) with ESMTPSA id 31BB662BD5
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 13 Jul 2015 12:55:15 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=betarho.net; s=mail;
t=1436792115; bh=K5fCR/7IfozRKWwU7CmCm/83U2zk0YPfeMGwR14BReA=;
h=Date:From:Subject:To:From;
b=P/gtMV1SrvGtMWUmSri//h5yNU5NNqN+05WTt2IbGYxow2eBm9Oi1eoeUbF6Ff9mm
+zAyXo/FWpJVNvfbJ4HlDZV5cdLciTa8WuFc5j6VhuA4C6kqlP6vhcFErprRk5a43v
xd4ETrWrYgtBCEVZIpsGOYvNYAAl8m+5Tjw4mvmg=
Mime-Version: 1.0
Date: Mon, 13 Jul 2015 12:55:14 +0000
Content-Type: multipart/alternative;
boundary="----=_Part_165_421399874.1436792114"
Message-ID: <c872dcb5d7538526a251829ec9d90afb@owncloud.betarho.net>
X-Mailer: RainLoop/1.9.1.333
From: "Alex Barcelo" <alex@betarho.net>
To: bitcoin-dev@lists.linuxfoundation.org
X-Spam-Status: No, score=2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FSL_HELO_NON_FQDN_1, HTML_MESSAGE,
RCVD_IN_PBL, RDNS_NONE autolearn=no version=3.3.1
X-Spam-Level: **
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: [bitcoin-dev] About hardware accelerators advantages for full-node
(not mining)
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2015 13:04:21 -0000
------=_Part_165_421399874.1436792114
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
I am searching for guidance and opinion in the subject's matter. I will b=
egin with my use case, too see whether my ideas makes sense or not.=0A=0A=
I have a Jetson TK1[1], which is a GPU (CUDA) powered development board. =
I thought that it may be a power-efficient device (in bitcoin environment=
), and thought about having it as a full-node. Either as a public full-no=
de, if it makes sense, or a local full-node, to allow my PCs to perform r=
elay onto the bitcoind in the Jetson. My idea is to run a bitcoind daemon=
on the Jetson as a node with high performance-per-watt (also cheap and r=
epurposable). A pure-CPU implementation of bitcoind will clog the CPU=0A=
=0AI assume that there are a bunch of heavy-compute highly-parallel funct=
ions which could be "outsourced" to a GPU. I may want to fork and/or cont=
ribute on that. However, maybe I am speaking nonsense. I have more backgr=
ound on parallel programming than my knowledge on bitcoin protocol. So, b=
efore coding a complete mess, I wanted to hear some opinions on the idea/=
configuration.=0A=0A[1] https://developer.nvidia.com/jetson-tk1
------=_Part_165_421399874.1436792114
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE html><html><head><meta http-equiv=3D"Content-Type" content=3D"t=
ext/html; charset=3Dutf-8" /></head><body><div data-html-editor-font-wrap=
per=3D"true" style=3D"font-family: arial, sans-serif; font-size: 13px;">I=
am searching for guidance and opinion in the subject's matter. I will be=
gin with my use case, too see whether my ideas makes sense or not.<br><br=
>I have a Jetson TK1[1], which is a GPU (CUDA) powered development board.=
I thought that it may be a power-efficient device (in bitcoin environmen=
t), and thought about having it as a full-node. Either as a public full-n=
ode, if it makes sense, or a local full-node, to allow my PCs to perform =
relay onto the bitcoind in the Jetson. My idea is to run a bitcoind daemo=
n on the Jetson as a node with high performance-per-watt (also cheap and =
repurposable). A pure-CPU implementation of bitcoind will clog the CPU<br=
><br>I assume that there are a bunch of heavy-compute highly-parallel fun=
ctions which could be "outsourced" to a GPU. I may want to fork and/or co=
ntribute on that. However, maybe I am speaking nonsense. I have more back=
ground on parallel programming than my knowledge on bitcoin protocol. So,=
before coding a complete mess, I wanted to hear some opinions on the ide=
a/configuration.<br><br>[1] https://developer.nvidia.com/jetson-tk1</div>=
</body></html>
------=_Part_165_421399874.1436792114--
|
