Re: Hardware acceleration?

Matthew Toseland <toad-EI5O+8PHWbJeeLb3ft/[email protected]> Fri, 12 Dec 2008 14:24:18 +0000
Newsgroups gmane.network.freenet.technical
Message-ID <[email protected]>
On Friday 12 December 2008 14:01, Daniel Cheng wrote:
> >>
> >> I just searched a bit for other hardware accelerators a bit and came
> >> across the Sun UltraSparc T2 again.
> >>
> >> If SHA-256 and DSA are the most common tasks within freenet I think that
> 
> We spend 40x more time on Rijndael then on SHA-256.
> The time spend on SHA256 is nothing.

That's because we use the JVM's native implementation of SHA-256.
> 
> >> would be the processor of choice for hardware acceleration, although it
> >> lacks a RNG or Rijndael of course.
> >
> > We also do a lot of Rijndael. Some hardware may be able to do Rijndael 
with a
> > 256 bit block size, I dunno exactly what operations the hardware actually
> > does.
> 
> They do NIST standard AES.
> Our Rijndael use the blocksize not in the standard.

They implement the full algorithm and can't be retasked? Ok.
> 
> > However, if you are actually queueing downloads, we also do a lot of FEC
> > decoding and encoding. Which can't be hardware accelerated.

_______________________________________________
Tech mailing list
[email protected]
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/tech
signature.asc (application/pgp-signature, 827 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQIVAwUASUJ0E3svjZi+xPTDAQIFWRAAgZQ8KU2wezXm9px80KbrpQ17KJq89jKC
lOKn583Lsy1/bpNuJCzihcusV/LucEmC+3ThPrFmKeFWOelMw4Q+bwQdPPouTCCE
CAL/ZoX7J5wu2Yy65oSegpfO1n3M4w+NfUGmtWmzg+yxdBvN98H09zGiQ8YbQdrt
7nSuvKIv69yHGJlrrtFxLnIo1llYB8wA4wtQDKORrpaWIc+hcvZFFDC5IQLoDwoN
mw7nJ9AS/w5BrPVLDG1sHomCUWVoYfDfEtAaHVaplWNpo2aZG2cPc4QWTmS5DEUe
wcJQ6l2ghSSAz/5eHBxb5q7r+HPr2bMnc+xdgESGunp8bZ1cz6O1f6ab6jso3V3Q
ADeIIn0sqy6hAXKwMklcClSxwG6RP/zDvH2cDpXOWNLlNLlHjBCg6MAR3hGMdFF7
Q7k00ceWdLh2eFWQ8/zdzXNleWYu/oc083cLkNI7Su2lSA+37lX++vs4DfiAHNjp
nnhu67rEUthjaF6fsAGR7Ao73mErf2ARV6ORHoTtRdUU5RaQSRB5ooqL7SjIT97H
X0RpvqebD2yGvQ+TVE0N+bRhma6d5AR9slwks7yefvp9Je3Iv+Ovkl0f6FA2ewlN
VCzK4TohSdx4oNqBM1DnG0sWyvSzyQFulcM0l+FrwNqmGJf6sXvX8otHtGuOuvLH
N12r2xeu9k4=
=wrWT
-----END PGP SIGNATURE-----