[parsec-users] How are pipeline threads synchronized in Dedup?

Akshatha mulki Bhat fdm546 at my.utsa.edu
Sat Mar 31 11:01:03 EDT 2012


Thanks!
Akshatha

On Sat, Mar 31, 2012 at 9:40 AM, Yungang Bao <ybao at cs.princeton.edu> wrote:

> Hi Akshatha,
>
> The synchronization operations are in these two functions -- enqueue() and
> dequeue() -- in the queue.c file.
> Dedup uses pthread_cond_wait() and pthread_cond_signal() to synchronize
> the producers and consumers of one queue.
>
> Yungang
>
> ----- Original Message -----
> From: "Akshatha mulki Bhat" <fdm546 at my.utsa.edu>
> To: "PARSEC Users" <parsec-users at lists.cs.princeton.edu>
> Sent: Friday, March 30, 2012 6:30:27 PM
> Subject: [parsec-users] How are pipeline threads synchronized in Dedup?
>
>
> Hi,
>
> I have a very basic question on the pipeline implementation of Dedup in
> PARSEC.
> I understand that there are many threads (maximum being
> MAX_THREADS_PER_QUEUE) working on a single queue at the intermediate
> pipeline stages. In order to enqueue/dequeue items into the queue, there is
> a counter variable(for ex: tmp_count) which keeps track of the number of
> items to enqueue at a time(this is implemented for chunking purpose, i.e.,
> atleast ITEMS_PER_FETCH amount of items are eneuqued/dequeued, in order to
> avoid lock contention on the queues). Although, what I don't understand is
> how are these counter variables synchronized among all the threads which
> work at the same time on a queue? Please let me know in these regards.
>
> Thanks
> Akshatha
>
> _______________________________________________
> parsec-users mailing list
> parsec-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/parsec-users
> _______________________________________________
> parsec-users mailing list
> parsec-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/parsec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/parsec-users/attachments/20120331/34db07eb/attachment.htm>


More information about the parsec-users mailing list