Re: [GSoC 2017] Number for sockets

2017-08-13 Thread Kalle Olavi Niemitalo
Kalle Olavi Niemitalo writes: > The following builds OK (also with LWIP_POLL=1 if you add > #include to cc.h) but I have not run it. Fixed a couple of bugs. Still not run. commit a5b178d9111d8bbc34f9a820cda56e20343fb2b0 Author: Kalle Olavi Niemitalo AuthorDate: 2017-08-13 14:43:29 +0300

Re: [GSoC 2017] Number for sockets

2017-08-13 Thread Kalle Olavi Niemitalo
Kalle Olavi Niemitalo writes: > The implementation effort might be 4 hours, not including testing > and publication. That was very accurate. The following builds OK (also with LWIP_POLL=1 if you add #include to cc.h) but I have not run it. Why do the files have CRLF in the lwip-hurd repositor

Re: [GSoC 2017] Number for sockets

2017-08-12 Thread Kalle Olavi Niemitalo
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

Re: [GSoC 2017] Number for sockets

2017-08-12 Thread Svante Signell
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