On Thursday, August 21, 2003, at 05:41 PM, rimas avizienis wrote: here's my situation. i've written a coreaudio driver to support a piece of custom hardware that transmits and receives digital audio over ethernet. my current driver communicates with the network interface by using dlil_attach_interface_filter to attach a callback function. this works fine for receiving packets and i transmit packets using dlil_inject_if_output. the problem with this driver is that when the machine is under a heavy load (running an audio synthesis program which does its computation in the high priority coreaudio callback thread) the outgoing packets don't get transmitted until the high priority thread relinquishes control (and then they get sent out in a big burst). this results in latency which i'm trying to minimize. i am presently trying to modify my coreaudio driver so that it speaks directly to the ethernet driver (bypassing the network stack entirely). Is this going to be for your own personal use, or to be distributed with your customer hardware that you hope to sell? If the latter, I would warn against anything that bypasses the network stack. -Michael _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.