From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [67.231.152.113]) by dpdk.org (Postfix) with ESMTP id 826E62B98 for ; Wed, 13 Jul 2016 12:30:42 +0200 (CEST) Received: from pps.filterd (m0000700.ppops.net [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.16.0.11/8.16.0.11) with SMTP id u6DARs54029127; Wed, 13 Jul 2016 03:30:40 -0700 Received: from brmwp-exmb11.corp.brocade.com ([208.47.132.227]) by mx0b-000f0801.pphosted.com with ESMTP id 242xw3v3bm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 13 Jul 2016 03:30:40 -0700 Received: from EMEAWP-EXMB12.corp.brocade.com (172.29.11.86) by BRMWP-EXMB11.corp.brocade.com (172.16.59.77) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Wed, 13 Jul 2016 04:30:39 -0600 Received: from EMEAWP-EXMB11.corp.brocade.com (172.29.11.85) by EMEAWP-EXMB12.corp.brocade.com (172.29.11.86) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Wed, 13 Jul 2016 12:30:37 +0200 Received: from EMEAWP-EXMB11.corp.brocade.com ([fe80::85ea:b7da:48dd:1640]) by EMEAWP-EXMB11.corp.brocade.com ([fe80::85ea:b7da:48dd:1640%21]) with mapi id 15.00.1156.000; Wed, 13 Jul 2016 12:30:37 +0200 From: Jan Blunck To: "thomas.monjalon@6wind.com" , "dev@dpdk.org" CC: "huawei.xie@intel.com" , "huilongx.xu@intel.com" , "thiagocmartinsc@gmail.com" Thread-Topic: DPDK on Xen maintenance Thread-Index: AQHR3CCMvxRQ9AddIU+rZ5SmzarLX6AWCWcA Date: Wed, 13 Jul 2016 10:30:36 +0000 Message-ID: <1468405836.28473.15.camel@brocade.com> References: <1795705.pPV7SVCssA@xps13> In-Reply-To: <1795705.pPV7SVCssA@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.250.1.134] Content-Type: text/plain; charset="iso-8859-15" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-07-13_03:, , signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 impostorscore=0 lowpriorityscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1607130112 Subject: Re: [dpdk-dev] DPDK on Xen maintenance X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2016 10:30:42 -0000 On Di, 2016-07-12 at 11:34 +0200, Thomas Monjalon wrote: > Hi all, >=20 > We are facing some issues with Xen dom0. > Some were fixed in RC2: > https://urldefense.proofpoint.com/v2/url?u=3Dhttp-3A__dpdk.org_ml > _archives_dev_2016- > 2DJuly_043760.html&d=3DCwICAg&c=3DIL_XqQWOjubgfqINi2jTzg&r=3DeGq7Pg5OSP44= 0n > QUcjb02I48YXd7Ce6OiSj9BMaGZiE&m=3D98n7rM-Tjze4nm2MUpU8Etvo5lAB- > oe0KXsst27ujkw&s=3DAHzBPDmKhqbsIc8pb2x_s7ShJvDhf93AsXRAm43EXlM&e=3D=A0 > and there still have some other issues. >=20 > It seems Xen is becoming less attractive: > - we do not have a lot of test reports or feedbacks > - there is no maintainer for DPDK on Xen > - we are still waiting for the Xen netfront PMD >=20 Although progress is slow I'm still working on upstreaming the Xen netfront PMD. I will continue to maintain it afterwards of course. > I wonder wether it still makes sense to maintain this code or not? > In case of positive reply, it would be nice to have the name of > someone responsible for this code, i.e. a maintainer. >=20 > Thanks=