search

maaars / cudpp

Automatically exported from code.google.com/p/cudpp
Other
0 stars 0 forks source link

Increase the maximum sizes of scans and segmented scans #45

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Segmented Scans and Scans doesnot work on very large array sizes.

Original issue reported on code.google.com by itz...@gmail.com on 13 Nov 2009 at 5:45

GoogleCodeExporter commented 8 years ago 
Updating labels.

Note, this makes a lot of sense for segmented scans.  For unsegmented scans, 
precision 
will become an issue for very large scans, so it makes less sense for 32-bit 
data 
types.

Original comment by harr...@gmail.com on 19 Nov 2009 at 1:37

GoogleCodeExporter commented 8 years ago 
Issue 58 has been merged into this issue.

Original comment by harr...@gmail.com on 23 Jun 2010 at 4:24

GoogleCodeExporter commented 8 years ago 
Hi,

Refer to the comment in issue 58, I would like to ask a question about this 
issue.

If my display card only support 512 threads of each blocks and 65535 blocks of 
1d grid, does it mean the scan function only support max 33,553,920 (512x65535) 
elements?

Original comment by lemon...@gmail.com on 8 Nov 2010 at 7:08

GoogleCodeExporter commented 8 years ago 
This becomes more important now with 64-bit type support.  But we're going to 
wait until release 2.1 to fix this due to time constraints.

Original comment by harr...@gmail.com on 6 Jul 2011 at 2:29