Re: [Chicken-hackers] [PATCH] Avoid context switch during TCP errno reporting

[Jörg F . Wittenberger]

On Mar 20 2013, Peter Bex wrote:

> On Wed, Mar 20, 2013 at 08:12:18PM +0100, Jörg F. Wittenberger wrote:
> > Not at all.  I forgot to mention: it relies only on
> > ##sys#thread-block-for-i/o! 
> > and skips the single-fd ##net#select-write stuff entirely
> > for the sake of fairer scheduling.
> > ...
> Do you think you could post a clean patch for introducing just this one
> change to tcp?  That would be great.  I'd have to dig in otherwise,
> anyway since I'd like to change tcp to avoid using select().

I'm afraid this is not completely possible.

So far I did not bother to provide /true/ READY? procedures
for the input ports.  Instead they return #t until the port is
closed.  (I don't have any use for this test. Instead of testing
whether or not the read would block I use to just read along
and have the thread blocked if needed.)

Doing a real READY? procedure is IMHO not going to work without
a single-fd poll.

Otherwise find the modifications attached.

Best Regards

(Jörg


.........

tcp.patch
Description: tcp.patch