Re: [PATCH] /dev/epoll update ...

["Christopher K. St. John" <cks@distributopia.com>]

Davide Libenzi wrote:
> 
> Here are examples basic functions when used with
> coroutines.
>
 
 I think all might be made clear if you did a quick
test harness that didn't use coroutines. I'm guessing
the vast majority of potential users will not be using
a coroutine library.

 On "nio-improve" page, you've got:

        for (;;) {
          evp.ep_timeout = STD_SCHED_TIMEOUT;
          evp.ep_resoff = 0;
          nfds = ioctl(kdpfd, EP_POLL, &evp);
          pfds = (struct pollfd *) (map + evp.ep_resoff);
          for (ii = 0; ii < nfds; ii++, pfds++) {
             ...
          }
        }

 Assume your server is so overloaded that you need
to avoid any unproductive calls to read() or write()
or accept(). Assume that instead of many very fast
connections coming in at a furious rate, you get a
large steady current of very slow connections.

 If you try to flesh out the above template with those
goals in mind, I think you'll quickly see what I've
been trying to get at with regard to the awkwardness
of not getting back some indication of the initial
state of the fd.

 The current situation isn't fatal, just awkward. And
fixable. For the low low price of a tiny bit of
idealogical purity...



-- 
Christopher St. John cks@distributopia.com
DistribuTopia http://www.distributopia.com