[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GSoC 2017] Number fo sockets
From: |
Kalle Olavi Niemitalo |
Subject: |
Re: [GSoC 2017] Number fo sockets |
Date: |
Sun, 13 Aug 2017 12:27:30 +0300 |
User-agent: |
Gnus/5.110007 (No Gnus v0.7) Emacs/23.0.51 (gnu/linux) |
Kalle Olavi Niemitalo <kon@iki.fi> writes:
> I wonder how hard it would be to implement those select ops in
> the translator without hogging a thread for each.
To clarify: if one thread in a program calls select on an fd_set
that lists ten sockets, then glibc sends ten io_select requests
before it waits for any response, and this costs ten threads in
the lwip translator if none of the sockets is ready. Adding
lwip_poll does not help with that. The struct lwip_select_cb
would have to be allocated from the heap and there would have to
be a way to unlink and free it if glibc destroys the reply port.
Re: [GSoC 2017] Number fo sockets, Kalle Olavi Niemitalo, 2017/08/13
- Re: [GSoC 2017] Number fo sockets, Joan Lledó, 2017/08/13
- Re: [GSoC 2017] Number fo sockets, Kalle Olavi Niemitalo, 2017/08/13
- Re: [GSoC 2017] Number fo sockets, Joan Lledó, 2017/08/15
- Re: [GSoC 2017] Number fo sockets, Joan Lledó, 2017/08/17
- Re: [GSoC 2017] Number fo sockets, Kalle Olavi Niemitalo, 2017/08/17
- Re: [GSoC 2017] Number fo sockets, Joan Lledó, 2017/08/23
- Re: [GSoC 2017] Number fo sockets, Kalle Olavi Niemitalo, 2017/08/23
Re: [GSoC 2017] Number fo sockets, Mark H Weaver, 2017/08/24