From: lm@bitmover.com (Larry McVoy) Date: Mon, 1 Oct 2007 19:20:59 -0700You're not showing us your test program so there is no way we can help you out. My initial inclination, even without that critical information, is to ask whether you are setting any socket options in way? In particular, SO_RCVLOWAT can have a large effect here, if you're setting it to something, that would explain why dd is doing better. A lot of people link to "helper libraries" with interfaces to setup sockets with all sorts of socket option settings by default, try not using such things if possible. You also shouldn't dork at all with the receive and send buffer sizes. They are adjusted dynamically by the kernel as the window grows. But if you set them to specific values, this dynamic logic is turned off. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| monstr | [PATCH 26/60] microblaze_v4: time support |
| Jon Smirl | Re: 463 kernel developers missing! |
| Andrew Morton | Re: x86: 4kstacks default |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
| Jiri Olsa | [PATCHv5 0/2] net: fix race in the receive/select |
