[<prev] [next>] [day] [month] [year] [list]
Message-ID: <loom.20140701T161608-685@post.gmane.org>
Date: Tue, 1 Jul 2014 15:19:35 +0000 (UTC)
From: Vadim Lebedev <vadim@...sys.com>
To: linux-kernel@...r.kernel.org
Subject: Questions about Optimizing network I/O
Hello,
I'm looking for advice on optimizing a SOCKS proxy software which i modified
to support TCP <=> UDP tunnelling.
The modification of standard SOCKS protocol is pretty straightforward, i've
added a command that tells to socks server that destination socket is a UDP
socket so the server expects the tcp packets for this destination to be
prefixed with 4 byte length. The server reads the length prefix the reads the
'length' bytes for the tcp stream and send the data (without the length
prefix) to the destination address as UDP datagram.
The return path (from UDP to TCP) is even simpler: The server read UDP
datagram into a buffer whre 4 bytes are reserved for length prefix, fill
this prefix with the length of just read packet and send the buffer to the
tcp socket.
When testing my SOCKS server i see that the TCP -> UDP processing generates a
lot o CPU load while UDP -> TCP or normal SOCKS TCP <=> TCP processing
generates relatively light cpu load.
So i'm looking for the way to optimize TCP -> UDP path.
My idea is to write a kernel module which will define an ioctl with 2 params
TCP_fd and UDP_fd and will do TCP to UDP processing completely in kernel mode
without copying data frmo/to skbufs....
Any ideas about this approach?
Thanks
Vadim
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists