> It's not the select that waits. It's a delay in the tcp send > path waiting for more data. Try disabling it: > > int f=1; > setsockopt(s, SOL_TCP, TCP_NODELAY, &f, sizeof(f)); Bingo! With this fix, 2.2.18 performance becomes almost identical to 2.4.0 performance. I assume 2.4.0 disables Nagle by default on local connections... Dan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: PROBLEM: select() on TCP socket sleeps for 1 tick ... Michael Lindner
- Re: PROBLEM: select() on TCP socket sleeps for 1 ... Michael Lindner
- Re: PROBLEM: select() on TCP socket sleeps fo... Edgar Toernig
- Re: PROBLEM: select() on TCP socket sleep... Dan Maas
- Re: PROBLEM: select() on TCP socket s... Michael Lindner
- RE: PROBLEM: select() on TCP soc... David Schwartz
- Re: PROBLEM: select() on TCP socket s... Michael Lindner
- Re: PROBLEM: select() on TCP soc... Stephen D. Williams
- Re: PROBLEM: select() on TCP... James Antill
- Re: PROBLEM: select() on... Stephen D. Williams
- Re: PROBLEM: select() on... James Antill
- Re: PROBLEM: select() on... Stephen D. Williams
- Re: PROBLEM: select() on... James Antill
- Re: PROBLEM: select() on TCP socket sleeps for 1 ... Dan Maas