From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44902) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZH8Mv-0003Bu-D2 for qemu-devel@nongnu.org; Mon, 20 Jul 2015 06:32:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZH8Mp-0003vZ-C5 for qemu-devel@nongnu.org; Mon, 20 Jul 2015 06:32:21 -0400 Received: from mail-wg0-x231.google.com ([2a00:1450:400c:c00::231]:34601) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZH8Mp-0003uu-4A for qemu-devel@nongnu.org; Mon, 20 Jul 2015 06:32:15 -0400 Received: by wgkl9 with SMTP id l9so126854125wgk.1 for ; Mon, 20 Jul 2015 03:32:13 -0700 (PDT) Date: Mon, 20 Jul 2015 11:32:08 +0100 From: Stefan Hajnoczi Message-ID: <20150720103208.GA12675@stefanha-thinkpad.redhat.com> References: <55AC9859.3050100@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: <55AC9859.3050100@cn.fujitsu.com> Subject: Re: [Qemu-devel] [POC] colo-proxy in qemu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Li Zhijian Cc: zhanghailiang , jan.kiszka@siemens.com, jasowang@redhat.com, "peter.huangpeng" , qemu-devel@nongnu.org, "Gonglei (Arei)" , stefanha@redhat.com, Yang Hongyang , dgilbert@redhat.com --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jul 20, 2015 at 02:42:33PM +0800, Li Zhijian wrote: > We are planning to implement colo-proxy in qemu to cache and compare packets. I thought there is a kernel module to do that? Why does the proxy need to be part of the QEMU process? -netdev socket or host network stack features allow you to process packets in a separate process. Without details on what the proxy does it's hard to discuss this. What happens in the non-TCP case? What happens in the TCP case? Does the proxy need to perform privileged operations, create sockets, open files, etc? The slirp code is not actively developed or used much in production. It might be a good idea to audit the code for bugs if you want to use it. Stefan --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVrM4oAAoJEJykq7OBq3PIRAcH/1Mz51noQwhTL99WNu/9JzAW mRGm6MLqIhaNZZE1yIt26OctgrKCqJ2QFlagyrmIEwRKEoqREwYG2ojEPHlTuBAI k0Ox1WqSWyMuxRktpevblxh4zKmv9ZgwHi1yr0etG6Odciq9q/erF5ZnxgAsbpoc Yxs2c20UB+E9UB6UtMrSQljjbjd46xtc2VFMc71MwTz+Vu0r286H8gxqH5KYPqnE UBBXmYRvBE/SnZw6K5XU9TaVFHvsapIQEOwOA/jhpXdKTGzefcajzmLkd9zT4U+5 WlE/CoWkCNvtN2FEuGB43P2ZjNG7rPyqpfbH+aSEZ+F6sTBygPHosUEBBlWo1N4= =wJvE -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q--