Svante Signell writes:
> How much effort is it to implement lwip_poll?
lwip_select constructs a struct lwip_select_cb on the stack
and adds that to the global linked list select_cb_list.
event_callback searches the list for structures that relate
to a particular socket, and wakes up the correspo
On Sat, 2017-08-12 at 19:24 +0300, Kalle Olavi Niemitalo wrote:
> Joan Lledó writes:
>
> > Since Glibc calls the io_select() operation each time the user
> > calls send() or recv(), in practice such sockets are just
> > unusable.
>
> Too bad there is no lwip_poll function.
> Might the LwIP folks
Joan Lledó writes:
> Since Glibc calls the io_select() operation each time the user
> calls send() or recv(), in practice such sockets are just
> unusable.
Too bad there is no lwip_poll function.
Might the LwIP folks be amenable to adding one?
> [3]
> https://github.com/jlledom/lwip-hurd/commi
As I mentioned in my previous post about ioctl operations[1], LwIP
establishes a maximum limit of sockets, which is a big problem for a
system like the Hurd. Now I've finished all tasks in my initial
proposal, I thought it was a good idea to spend some time studying
this issue and trying to find a
