[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: destroying buckets and classes, terminating server loops
From: |
Marcus Brinkmann |
Subject: |
Re: destroying buckets and classes, terminating server loops |
Date: |
Tue, 16 Jul 2002 22:08:53 +0200 |
User-agent: |
Mutt/1.4i |
On Fri, Jul 05, 2002 at 02:34:27PM -0400, Roland McGrath wrote:
> > The issue I am facing is that in the console client library, to make the
> > notify mechanism work, I have to put each notification request into its own
> > port bucket. This is so that I can set the queue limit to a very low value,
>
> This is madness. What makes you think you need separate buckets,
> i.e. separate port sets? The qlimit is on a port, not a port set.
The problem is quite a different one. I need to use
ports_manage_port_operations_one_thread, because if I use multithreads,
the queue limit is ineffective for my application.
So I need to have exactly one thread for each virtual console that I am
handling, which means I need separate buckets.
The library should be generic enough to support arbitrary number of virtual
consoles open at a time, depending on what is presented to the user.
The only alternative I see is to cache unused buckets and operations running
on them.
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' GNU http://www.gnu.org marcus@gnu.org
Marcus Brinkmann The Hurd http://www.gnu.org/software/hurd/
Marcus.Brinkmann@ruhr-uni-bochum.de
http://www.marcus-brinkmann.de/