Re: [Ggnfs-devel] overhaul of pol5

[Stanislav V. <st...@ma...>]

Hi Jason,

Usually a new sources branch is being created for this king of stuff.
But, considering quite inactive ggnfs development, it should be safe
to place the modified pol51m0b into the trunk branch. Maybe here:
.\trunk\src\experimental\pol5 ?

Personally, I do not think it would be a much harm to replace the
existing pol51m0b implementation, providing you've tested it carefully.
But, I may turn to be a bad idea until people test new pol51m0b on
different platforms and configurations. And they won't until you
replace the existing implementation.. :)

    Stanislav

JP> It was a little dicey at times but I think I have pol51m0b in
JP> better shape now. The source is reformatted and split over 
JP> multiple files, dead code is removed, and almost all the global 
JP> variables are now packed into local structures that are allocated 
JP> and freed (this was very painful). Finally, the main code has 
JP> been split off into a library with a very minimal API. If you don't
JP> use the assembly code, it's actually thread-safe :)

JP> Performance is the same, output is identical in all my tests
JP> (these are actually just running the complete binary for a little
JP> while on RSA100-140). I want to commit what I have before continuing 
JP> the cleanup and moving on to optimizations, and I don't want to 
JP> disturb the current pol5 directory. Where would a good place be to 
JP> put the modified code?

JP> jasonp


JP> ------------------------------------------------------
JP> This message was sent using BOO.net's Webmail.
JP> http://www.boo.net/

JP> -------------------------------------------------------------------------
JP> This SF.net email is sponsored by: Microsoft
JP> Defy all challenges. Microsoft(R) Visual Studio 2005.
JP> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
JP> _______________________________________________
JP> Ggnfs-devel mailing list
JP> Ggn...@li...
JP> https://lists.sourceforge.net/lists/listinfo/ggnfs-devel