mersenneforum.org  

Go Back   mersenneforum.org > Great Internet Mersenne Prime Search > Software

Reply
 
Thread Tools
Old 2011-10-17, 09:22   #12
LaurV
Romulan Interpreter
 
LaurV's Avatar
 
Jun 2011
Thailand

2·5·312 Posts
Default

Quote:
Originally Posted by axn View Post
128-bit floating point implemented in hardware could speed up LL testing by 2x. Even implemented in microcode, it could potentially speed it up by 25%.
You may be right, but I did not see any 128-bit-FPALU in RL yet. Maybe there are, but I don't know of any.
LaurV is offline   Reply With Quote
Old 2011-10-17, 13:53   #13
R.D. Silverman
 
R.D. Silverman's Avatar
 
Nov 2003

22·5·373 Posts
Default

Quote:
Originally Posted by LaurV View Post
I don't believe OP was asking about memory width. I took it like CPU register size, and since my previous post.

<snip>

Maybe we will never go to more then 64 bit addressing space, as said before, this is more then enough for how much memory one can have in its box,

<snip>

The question is if this would speed up searching for huge primes. My answer stands: with the current algorithms, most probably not, or not so much. Having a 3x or 4x speed for TF means nothing, you could do one or two bits more. The real gain would come from discovering new algorithms, as somebody said on a parallel thread.
It is so refreshing to read common sense!!!! But I strongly doubt
whether a faster algorthm than LL exists.

128-bit registers would help somewhat, but would only be a constant factor
speedup. And that can easily be obtained now by additional cores --> no
architectural changes required.

There is no market today (well, almost no market) for a machine with
128-bit registers. Think about the economics of developing such a
processor.

OTOH, there is a small market for perhaps a 128-bit arithmetic coprocessor
implemented as (say) a PCI card. But if I were to develop such a device,
I certainly would not limit it to 128-bits. I'd build a board level coprocessor
with (say) 1024-bit registers. In fact, when I was at MITRE we designed
and built a VMW-based board (done in prototype wire-wrap using TI DSP
chips) that implemented 1024-bit arithmetic as a coprocessor to a SPARC.
[It was just a research project].

I strongly doubt whether there is sufficient demand to make development
of a commercial MP processor economically viable.

GIMPS has no real practical importance. It will find the next prime when it
finds it. Patience!
R.D. Silverman is offline   Reply With Quote
Old 2011-10-17, 16:25   #14
chris2be8
 
chris2be8's Avatar
 
Sep 2009

40368 Posts
Default

Quote:
Originally Posted by Dubslow View Post
Well, even from a memory standpoint, I wouldn't be surprised if it became necessary sometime way off in the future. I'm sure someone in the late 40's/early 50's said &quot;we'll never ever get anywhere close to 4 GB of memory, 32 bits is more than enough&quot; and look at where we are now.
When IBM designed the system 360 in the 1960s they said 24 bits would be enough. As a ex systems programmer on the platform's successors I can testify that was *big* a mistake. It was subsequently extended, first to 31 bits (don't ask why not 32), then to 64 bits. But with lots of 24 bit only code still around the complications it caused were a big pain.

Chris K
chris2be8 is offline   Reply With Quote
Old 2011-10-17, 16:29   #15
chris2be8
 
chris2be8's Avatar
 
Sep 2009

2·1,039 Posts
Default

Quote:
Originally Posted by R.D. Silverman View Post
There is a small market for perhaps a 128-bit arithmetic coprocessor
implemented as (say) a PCI card. But if I were to develop such a device,
I certainly would not limit it to 128-bits. I'd build a board level coprocessor
with (say) 1024-bit registers.
The most likely market would be for a public key accelerator doing 1024 or 2048 bit arithmetic. As long as it's not crippled to limit the max data length it would be helpful.

Chris K
chris2be8 is offline   Reply With Quote
Old 2011-10-17, 16:41   #16
R.D. Silverman
 
R.D. Silverman's Avatar
 
Nov 2003

164448 Posts
Default

Quote:
Originally Posted by chris2be8 View Post
The most likely market would be for a public key accelerator doing 1024 or 2048 bit arithmetic. As long as it's not crippled to limit the max data length it would be helpful.

Chris K
We already have such hardware. Banks use it. Current performance is more than adequate.
R.D. Silverman is offline   Reply With Quote
Old 2011-10-17, 17:14   #17
fivemack
(loop (#_fork))
 
fivemack's Avatar
 
Feb 2006
Cambridge, England

72×131 Posts
Default

Moreover, the highest-end hardware security modules used by banks have about one-third the performance of an i7/2600 CPU when doing 1024-bit or 2048-bit RSA (I have a friend who works for a company that makes them).
fivemack is offline   Reply With Quote
Old 2011-10-17, 17:39   #18
R.D. Silverman
 
R.D. Silverman's Avatar
 
Nov 2003

22·5·373 Posts
Default

Quote:
Originally Posted by fivemack View Post
Moreover, the highest-end hardware security modules used by banks have about one-third the performance of an i7/2600 CPU when doing 1024-bit or 2048-bit RSA (I have a friend who works for a company that makes them).
"A company"? I presume that you mean IBM.
R.D. Silverman is offline   Reply With Quote
Old 2011-10-17, 17:42   #19
ixfd64
Bemusing Prompter
 
ixfd64's Avatar
 
"Danny"
Dec 2002
California

45268 Posts
Default

This reminds me, AVX is supposed to support 512- and 1024-bit registers in the future. But whether we will actually have them remains to be seen.
ixfd64 is offline   Reply With Quote
Old 2011-10-28, 13:24   #20
E_tron
 
E_tron's Avatar
 
Sep 2002
Austin, TX

3×11×17 Posts
Default

A modern FPGA might be fast enough to implement the 1024-bit arithmetic coprocessor your thinking about R.D. Silverman. Perhaps we should stick with 64-bit commodity hardware instead . Commodity hardware is highly optimized and might/probably will outperform a custom design on an FPGA anyway.
E_tron is offline   Reply With Quote
Old 2011-10-28, 14:56   #21
fivemack
(loop (#_fork))
 
fivemack's Avatar
 
Feb 2006
Cambridge, England

191316 Posts
Default

Quote:
Originally Posted by R.D. Silverman View Post
"A company"? I presume that you mean IBM.
nCipher (now Thales) of Cambridge; make 'hardware security modules', maybe more for internet than banking businesses but also sell to (for example) the UK Passport Agency
fivemack is offline   Reply With Quote
Old 2011-10-28, 15:03   #22
fivemack
(loop (#_fork))
 
fivemack's Avatar
 
Feb 2006
Cambridge, England

72·131 Posts
Default

Quote:
Originally Posted by E_tron View Post
A modern FPGA might be fast enough to implement the 1024-bit arithmetic coprocessor your thinking about R.D. Silverman. Perhaps we should stick with 64-bit commodity hardware instead . Commodity hardware is highly optimized and might/probably will outperform a custom design on an FPGA anyway.
I spent quite a while both in amateur and professional contexts contemplating large multipliers on FPGA, and could never get them to be remotely performance-per-pound competitive with Opterons. The individual multipliers are small and slow (25-bit x 18-bit, both signed, feeding a 48-bit accumulator, running at 638MHz), so you need about sixty of them to compete with one Opteron core, and the price of a single FPGA dev board gets you a complete off-the-shelf box with 48 Opteron cores.
fivemack is offline   Reply With Quote
Reply



Similar Threads
Thread Thread Starter Forum Replies Last Post
GIMPS on PS3 flouran Hardware 202 2010-04-30 09:06
GIMPS Nub SayMoi Information & Answers 5 2009-04-06 15:29
GIMPS uses only 1 cpu Unregistered Information & Answers 7 2009-01-10 20:01
GIMPS should pay Vijay Lounge 40 2005-07-01 18:10
Why do you run GIMPS ? Prime Monster Lounge 12 2003-11-25 19:04

All times are UTC. The time now is 13:06.


Fri Jul 16 13:06:59 UTC 2021 up 49 days, 10:54, 2 users, load averages: 1.97, 1.88, 1.67

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.