You are queueing pixel by pixel. But the threads can calculate (x,y) by themselves. Why not do the following:
my $width = 1280 * 4;
my $height = 1024 * 4;
$picturesize = $width * $height;
for(my $i=0; $i< $picturesize-1; $i+=32){
$start = $i;
$end = $i+32;
$x1 = int(($start % $width) /4);
$y1 = int(($start / $width) /4);
$x2 = int(($end % $width) /4);
$y2 = int(($end / $width) /4);
printf("(%4d,%4d)..(%4d,%4d) %d\n",
$x1,$y1,$x2,$y2, $i);
}
This way, the main program only uses the picture size (a large integer), and increases it by 32 units (4 pixels with four byte RGBA perl pixel, I guess). And you give it a start and stop range: $i .. $i+32. The thread can then use those numbers to calculate back the pixels (x,y) themselves, in parallel.
startthread($from,$to,$width)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|