From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <huawei.xie@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id E38E8559C
 for <dev@dpdk.org>; Mon, 25 Jan 2016 11:17:47 +0100 (CET)
Received: from fmsmga001.fm.intel.com ([10.253.24.23])
 by orsmga101.jf.intel.com with ESMTP; 25 Jan 2016 02:17:46 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.22,343,1449561600"; d="scan'208";a="888651567"
Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206])
 by fmsmga001.fm.intel.com with ESMTP; 25 Jan 2016 02:17:46 -0800
Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by
 FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Mon, 25 Jan 2016 02:17:46 -0800
Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.215]) by
 shsmsx102.ccr.corp.intel.com ([169.254.2.172]) with mapi id 14.03.0248.002;
 Mon, 25 Jan 2016 18:17:44 +0800
From: "Xie, Huawei" <huawei.xie@intel.com>
To: Tetsuya Mukawa <mukawa@igel.co.jp>, "dev@dpdk.org" <dev@dpdk.org>,
 "yuanhan.liu@linux.intel.com" <yuanhan.liu@linux.intel.com>, "Tan, Jianfeng"
 <jianfeng.tan@intel.com>
Thread-Topic: [RFC PATCH 5/5] virtio: Extend virtio-net PMD to support
 container environment
Thread-Index: AdFXWaE0AunQ5LVPT++h9TW0MGQ/9A==
Date: Mon, 25 Jan 2016 10:17:44 +0000
Message-ID: <C37D651A908B024F974696C65296B57B4C5ACAF4@SHSMSX101.ccr.corp.intel.com>
References: <1453108389-21006-2-git-send-email-mukawa@igel.co.jp>
 <1453374478-30996-6-git-send-email-mukawa@igel.co.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.239.127.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] [RFC PATCH 5/5] virtio: Extend virtio-net PMD to
 support container environment
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2016 10:17:48 -0000

On 1/21/2016 7:09 PM, Tetsuya Mukawa wrote:=0A=
> +static void=0A=
> +qtest_handle_one_message(struct qtest_session *s, char *buf)=0A=
> +{=0A=
> +	int ret;=0A=
> +=0A=
> +	if (strncmp(buf, interrupt_message, strlen(interrupt_message)) =3D=3D 0=
) {=0A=
> +		if (rte_atomic16_read(&s->enable_intr) =3D=3D 0)=0A=
> +			return;=0A=
> +=0A=
> +		/* relay interrupt to pipe */=0A=
> +		ret =3D write(s->irqfds.writefd, "1", 1);=0A=
=0A=
How about the interrupt latency? Seems it is quite long.=0A=
=0A=
> +		if (ret < 0)=0A=
> +			rte_panic("cannot relay interrupt\n");=0A=
> +	} else {=0A=
> +		/* relay normal message to pipe */=0A=
> +		ret =3D qtest_raw_send(s->msgfds.writefd, buf, strlen(buf));=0A=
> +		if (ret < 0)=0A=
> +			rte_panic("cannot relay normal message\n");=0A=
> +	}=0A=
> +}=0A=
=0A=