Hello Everyone,
Im getting ready to start up a new project at work, something to replace one I did over a year ago.
One of the problems I find myself running into is the amount of memory the older program is using. So I was looking at different ways to get around that, while at the same time improving on the functionality of what I already have.
In a nutshell the program is a data integrity tool that reads and writes to a specified file. One instance, one file, one process ... a very linear approach.
I use several small mallocs to setup read/write buffers but one big malloc to maintain a "virtual" list of where I need to read and write from. I use that list to ensure I have written to every block in that file. 99% of the code is Ansi C, I try very hard to avoid windows specific calls/library functions, thats allowed me to port this to linux with verfy few ifdefs to isolate windows or linux only code.
In an effort to cut down on the # of large mallocs I was thinking about going to one main process that tracked and handled the large list while smaller processes handle the read/write portion. The idea being the smaller process checks out a section to work with and then checks back in the results before checking a new task back out. This means data has to flow both directions.
--
So now to the meat of the question.
Is the threading thats in Pelles C posix compliant
Will Pelles C work with
http://sourceware.org/pthreads-win32/Peace
