[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fixing select
From: |
Richard Braun |
Subject: |
Re: Fixing select |
Date: |
Fri, 27 Jul 2012 11:51:20 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Wed, Jul 25, 2012 at 06:34:02PM +0200, Richard Braun wrote:
> For now, this branch only adds support for server-side timeouts. The
> select implementation in glibc still needs to be changed to use the new
> call when appropriate.
The change I want to apply means io_select calls must be asynchronous,
as replies will normally be processed by _hurd_select through a port
set. But io_select is declared as a routine in io.defs. While it's
relevant to keep it a routine for server side stub code generation, it
should be a simpleroutine when built in glibc (instead of a routine with
a timeout of 0). What's the recommended way to do that ? Is there a
macro I can use to cleanly identify what the stub code is built for,
e.g. a macro indicating that user stub code is generated ?
--
Richard Braun
- Fixing select, Richard Braun, 2012/07/25
- Re: Fixing select,
Richard Braun <=