[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: some performance problems with async console client
From: |
Roland McGrath |
Subject: |
Re: some performance problems with async console client |
Date: |
Fri, 14 Jun 2002 18:00:26 -0400 (EDT) |
> On Fri, Jun 14, 2002 at 05:01:02PM -0400, Roland McGrath wrote:
> > > > (well, ports_manage_multithreaded is still necessary, as Mach
> > > > doesn't let you receive messages in the order they were sent easily)
> >
> > I'm not sure what Marcus means here. Messages are dequeued from a
> > particular port in the order they were sent (if sending was serialized).
> > You can receive on a particular port (or on a portset containing no other
> > ports) and you will get them in order.
>
> Oh, that... mmh. That means I should use
> ports_manage_port_operations_one_thread, instead multithread ;)
You can make a special bucket for the port and use ..._one_thread in its
own thread, yes.