[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Proc
From: |
Ognyan Kulev |
Subject: |
Re: Proc |
Date: |
Wed, 6 Jun 2001 18:59:46 +0300 |
User-agent: |
Mutt/1.3.15i |
On Wed, Jun 06, 2001 at 06:44:41PM +0300, Ognyan Kulev wrote:
> Forwarded because of mistaken Cc: hurd-hurd@gnu.org
>
> On Wed, Jun 06, 2001 at 06:37:39PM +0300, Ognyan Kulev wrote:
> > On Wed, Jun 06, 2001 at 11:28:37AM -0500, Neal H Walfield wrote:
> > > > BTW Why in proc/main.c there is global_lock that is used in
> > > > message_demuxer
> > > > if proc is single-threaded?
> > >
> > > This is where everything is serialized.
> >
> > If there is only one thread, what is the need to be serialized?
> >
> > 1. Wait for a message
> > 2. Read it
> > 3. Execute it
> > 4. Go to 1
Sorry, now i see that proc is multithreaded, but the global lock is used to
execute RPC calls sequentially.
Regards
--
Ognyan Kulev <ogi@fmi.uni-sofia.bg>, "\"Programmer\""
- Re: MIG manuals, Ognyan Kulev, 2001/06/06
- Message not available
- Message not available
- Re: Proc, Ognyan Kulev, 2001/06/06
- Re: Proc,
Ognyan Kulev <=
- Re: MIG manuals, Marcus Brinkmann, 2001/06/06