Messages in this thread |  | | | Date | Thu, 27 Nov 2003 00:01:45 +0100 | | From | Andi Kleen <> | | Subject | Re: Fire Engine?? |
| |
On 26 Nov 2003 10:00:09 -0500 Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> >>>>> " " == Andi Kleen <ak@suse.de> writes: > > > - If they tested TCP-over-NFS then I'm pretty sure Linux lost > ^^^^^^^^^^^^ That would be inefficient 8-)
grin.
> > badly because the current paths for that are just awfully > > inefficient. > > ...mind elaborating?
Current sunrpc does two recvmsgs for each record to first get the record length and then the payload.
This means you take all the locks and other overhead twice per packet.
Having a special function that peeks directly at the TCP receive queue would be much faster (and falls back to normal recvmsg when there is no data waiting)
But that's the really obvious case. I think if you got out an profiler and optimized carefully you could likely make this path much more efficient. Same for sunrpc TX probably, although that seems to be in a better shape already.
-Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |