[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: output streams vs output ports

This page is part of the web mail archives of SRFI 68 from before July 7th, 2015. The new archives for SRFI 68 contain all messages, not just those from before July 7th, 2015.

From: Michael Sperber <sperber@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: output streams vs output ports
Date: Sun, 19 Jun 2005 11:09:16 +0200

> Could you clarify what would be expensive about it?  Getting the
> synchronization right is sure difficult to program, but I don't think
> there's a necessarily large performance hit.  (Specifically, Scheme 48
> does it all entirely without locking.)

Is there a portable way (i.e. can be written in portable C)
to avoid calling synchronization primitives (e.g. pthread_mutex_lock)
if the implementation uses native threads?

If I can sacrifice portability a bit, I may use spin lock with
processor-specific synchronization instruction.  (I also need
pthread_cleanup_push/pop to handle cancellation, but I expect
they are lightweight.)

Using pthread mutex and condition variables does hurt.  I'll be
glad if there's a better way.