Thanks for the write-up. I did not fully grok what the problem was with Mach ports. It turns out that we had the same performance problem on Windows when I tried converting IPC::Channel over to using base::ObjectWatcher (i.e., RegisterWaitForSingleObject) due to the thread context switching overhead. -Darin
On Fri, Dec 12, 2008 at 1:38 PM, Jeremy Moskovich <[email protected]>wrote: > The Linux/OS X IPC code is now in the tree. I still need to fix a few > things and land a refactoring for message_pump_libevent but by and large > whats in there should be useable. > > Having said that, my intent going forward is to continue bringing up > surrounding infrastructure, so if you plan on touching the IPC > infrastructure on Linux/OS X please ping me first to prevent duplicate > efforts. > > I've updated the Main IPC design doc with Linux/OS X information: > > http://sites.google.com/a/chromium.org/dev/developers/design-documents/inter-process-communication > > <http://sites.google.com/a/chromium.org/dev/developers/design-documents/inter-process-communication%20> > > and have also updated the Mach implementation page with an explanation of > why we aren't using that approach: > > > http://sites.google.com/a/chromium.org/dev/developers/design-documents/os-x-interprocess-communication > > Edits and additions are of course welcome. > > Best regards, > Jeremy > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
