Brian Somers wrote: > > "Scott Hess" wrote: > > > > > I've found an odd performance issue that I cannot explain. I'm using > > > socketpairs to communicate with multiple rfork(RFPROC) processes. > > > > Use 'pipe(2)' rahter than 'socketpair(2)' as both are bidirectional and > > pipe is a LOT faster. > > Although pipe(2)'s bi-directional capabilities are not standard (I've > been stung by this in the past :-() Neither is rfork()... Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Performance issue with rfork() and single socketpairs ver... Scott Hess
- Re: Performance issue with rfork() and single socket... Matthew Dillon
- Re: Performance issue with rfork() and single so... Scott Hess
- Re: Performance issue with rfork() and singl... Scott Hess
- Re: Performance issue with rfork() and singl... Matthew Dillon
- Re: Performance issue with rfork() and s... Alfred Perlstein
- Re: Performance issue with rfork() ... Scott Hess
- Re: Performance issue with rfork() and single socket... Peter Wemm
- Re: Performance issue with rfork() and single so... Brian Somers
- Re: Performance issue with rfork() and singl... Peter Wemm
- Re: Performance issue with rfork() and singl... Brian D. Moffet
- Re: Performance issue with rfork() and s... Peter Wemm
- Re: Performance issue with rfork() and s... James Bailie

