> ...and I still don't understand why the identical program, but using one > socket instead of 2 sockets, IS CPU bound, and gets on the order of > 10K/sec. on the same HW. Diffs to produce 10K/sec. 1 socket version from > my previous sample follow... It's really this simple -- this isn't what TCP is intended for. DS - 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
- Re: PROBLEM: select() on TCP socket sleeps fo... Michael Lindner