From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 03976A056A for ; Thu, 11 Mar 2021 01:17:29 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D4E1422A666; Thu, 11 Mar 2021 01:17:29 +0100 (CET) Received: from mx0a-00000d04.pphosted.com (mx0a-00000d04.pphosted.com [148.163.149.245]) by mails.dpdk.org (Postfix) with ESMTP id 4DA4C22A63E; Thu, 11 Mar 2021 01:17:27 +0100 (CET) Received: from pps.filterd (m0102888.ppops.net [127.0.0.1]) by mx0a-00000d04.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 12B0HHAL026504; Wed, 10 Mar 2021 16:17:27 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stanford.edu; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=pps05272020; bh=W9GQvyVN5mHq6qoT+3YGthQtLI+aCLxT1ZUp2OWMfTg=; b=ZAJsHfw7QjTvomjQzL1c1/38x5BhChyBxYYWHFV6Fu6Z8EX7jdklQngIz+BiHbJEKE3b yWbLsufnTeVSpanMQPkGV82uTIj8zgcwWVdiNiiDP4xJgP95pmjwNPBavS3f+utK7szZ 4xIApChUsTA+kj8mqAtHAvKWqn+mq6DNh5AD3tln3vgHbC42+ma0GbZhLxrQrkd3WsD2 7zKKaDpOz3LtHqcVhYd9D546TsWFmT8TfPZRbUPDzBSlw67W31GAqMNrtesTjVaSMC+W e9EGcgQ4ZrnGN9YJ0npt78gQ5NCmGyaGxuBDTxFfI6KKsMBXHdLMtryh0iwBc7no56Xy 5A== Received: from mx0a-00000d03.pphosted.com (mx0a-00000d03.pphosted.com [148.163.149.244]) by mx0a-00000d04.pphosted.com with ESMTP id 37470f6085-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 10 Mar 2021 16:17:26 -0800 Received: from pps.filterd (m0102881.ppops.net [127.0.0.1]) by mx0a-00000d03.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 12B0H2V4005136; Wed, 10 Mar 2021 16:17:26 -0800 Received: from mx0b-00000d06.pphosted.com (mx0b-00000d06.pphosted.com [148.163.139.119]) by mx0a-00000d03.pphosted.com with ESMTP id 3747j4e1r1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 10 Mar 2021 16:17:26 -0800 Received: from pps.filterd (m0167940.ppops.net [127.0.0.1]) by mx0b-00000d06.pphosted.com (8.16.0.43/8.16.0.43) with SMTP id 12B0HIHa024983; Wed, 10 Mar 2021 16:17:25 -0800 Received: from nam10-dm6-obe.outbound.protection.outlook.com (mail-dm6nam10lp2108.outbound.protection.outlook.com [104.47.58.108]) by mx0b-00000d06.pphosted.com with ESMTP id 3746r5x8hd-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 10 Mar 2021 16:17:25 -0800 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iaTHjQ4xkwcQ3bZ7ppfNUvGyqlPwVfoolQkpmCMNRt9rOgHQpKkiu4sIx64jsW+1iiyRLwqm6McvPyYScuHobXF0YDo4slylwkF5QHJz5hpuajO6+j+HsJT89uRlYo+2O6jZAJZu9ygrRmXjxxwmnglkIAuF8/U8MqmwdkouYQj53BslF3QM6y4uWMksYeidaJJnZ4w8MlMtveTCQ0kaBt6eZExVOEBIDH8vDQv/IfiPoH7bo99a9yRlMRJT9Y4ofSbkhE93tYzJnadximCb2GsPJN6FplBd3U/ZevJm+w1JulLQ/L2tsocfG8gX8TtUcDX6JAWjnjmXD8OgVlIgnw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=W9GQvyVN5mHq6qoT+3YGthQtLI+aCLxT1ZUp2OWMfTg=; b=A6LvsXWJAsYZ33Bn6x4KkkPaasdsAMnCAnY3HrIkDUoQS4vCX4iJiBPYqWqGSlOwpFRhJqXxSBUp5KxlqiNaS2iveMn+qiXbu4Daps0EFxYgpXotKLeNjkdxi9BO+EumdFssYSxIWYbhfSl310KKj9FxvsBdnOSh36jE2gZIYr0CEUQVAH3WulfLOpZ8CMPgNIDhJZh5D4OTqRDTZM6LYffhTInsbpxFWFYA9fvxUxQCvQYRwBioQyr1eOkp3MC0Xv1c0RIj/RHKY1NZ36auW3zBmH1xAv5C3e9bCGXCWBAzscrLxjOqpjPcclz2Ov1PFjMh868o4F8OiUuwgmg33A== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=stanford.edu; dmarc=pass action=none header.from=stanford.edu; dkim=pass header.d=stanford.edu; arc=none Received: from BYAPR02MB4613.namprd02.prod.outlook.com (2603:10b6:a03:57::33) by BYAPR02MB5400.namprd02.prod.outlook.com (2603:10b6:a03:95::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3912.30; Thu, 11 Mar 2021 00:17:23 +0000 Received: from BYAPR02MB4613.namprd02.prod.outlook.com ([fe80::3d7b:db38:f583:d155]) by BYAPR02MB4613.namprd02.prod.outlook.com ([fe80::3d7b:db38:f583:d155%3]) with mapi id 15.20.3912.030; Thu, 11 Mar 2021 00:17:23 +0000 From: Jinkun Geng To: Thomas Monjalon CC: Stephen Hemminger , "ci@dpdk.org" , "users@dpdk.org" Thread-Topic: [dpdk-ci] [dpdk-users] Integration of DPDK into Bazel Thread-Index: AQHXFIKDJvRyIqmyuUOkYOh6cX2eHqp674uAgAAbsW2AAtgigIAAAFbigAAIFgCAAABJvg== Date: Thu, 11 Mar 2021 00:17:23 +0000 Message-ID: References: <11457967.n7LkdMVPTe@thomas> , <3003733.ML7hmrJNhH@thomas> In-Reply-To: <3003733.ML7hmrJNhH@thomas> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: monjalon.net; dkim=none (message not signed) header.d=none;monjalon.net; dmarc=none action=none header.from=stanford.edu; x-originating-ip: [128.12.122.129] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 80177aa5-4199-4867-85bf-08d8e4230b48 x-ms-traffictypediagnostic: BYAPR02MB5400: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: tu10ktmrPNyzEUEYEHKjgkeg5jjzoQJXat3/7YVPmUdMDacCBiivBgvebzCnE52/n/C9VEHDraW/oJPnFZ/W9faTK5oVETp6/NiOtvxgPoiElGB9/PW66+a6Up1oMHqDnPfe4TVdY9+mgHxRONPUpYVUuZGtAyZlPKMaS1AaGk3zqLuxhTzDrB7BJsrbVWbyJHdQifOPDOzTQsUWkra8uyDQLqpnhnJXfI4BKQjR7moYocwuDAwaRgLJRE8EJIFgUX2k4WUnzwasesOFSnads+HIVbjxNCl/AWcJ3ZBXe9c2p8Rv8dXhIbIqPBook9AUN8d1rSjFhpyPUCDSlPa+AgSP/d99B1nL4cEhbc4TwO8KiHvVjBqMkosAcuHVgOdpc7KtuPq5A6arE60ragcOTtzFdxWb3YSKIJqq6HhEBPcKxrOUPsZZLvDR53q0HgTeHUHAlbW+IYwwwsRwzFlQKeNmmQQMQDzEugJrys39f7lOF6LzRwNr/vS+hPOrSV1U7Rlahx222VJz3xP9ngDnSBqFQ1pWODNi/v1vdeNIj4g+w0PTjj4QueAREp27ec26jNyePY3tdXDf6rA1qTpHyi5jTWXUYuMcK6kiChYPVbY= x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR02MB4613.namprd02.prod.outlook.com; PTR:; CAT:NONE; SFS:(346002)(376002)(136003)(396003)(39860400002)(366004)(66946007)(66446008)(66556008)(64756008)(83380400001)(66476007)(26005)(6506007)(5660300002)(19627405001)(53546011)(54906003)(75432002)(478600001)(76116006)(316002)(786003)(966005)(166002)(186003)(6916009)(52536014)(4326008)(7696005)(2906002)(9686003)(86362001)(55016002)(33656002)(8936002)(71200400001)(8676002); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata: =?us-ascii?Q?KNfpREq42g0D639JYNKwvN3s3mGCfPJ6DurrUK+i/o5yBhiaZxEpTA+LqG0Y?= =?us-ascii?Q?JjtxELMm2AyhqvMP6NhrfxiGeSFlHOy7gH0CcqeBPkPdubx21/X4C7awALPL?= =?us-ascii?Q?rOv5aWe+SnbYCen2vZt17sLqm3/CnQ1VwpORXSgqo2VRKLWKD22rufJtMXkg?= =?us-ascii?Q?aD4ItHfi3D0gh7Rev9kAUxH2GsSnVIeEl3mbflCyVQmhwmVeYHAOfogD2O2Y?= =?us-ascii?Q?EZuUw/dMVV7Z04SD/bNX/kmmv2zz/4Ans2DggatnS3upJ83NbKMzi2NtVPGM?= =?us-ascii?Q?IXedsIXe5DTGwt4Amc55nRyr86IvJOvJi3+L+JnPfylTuW21x9Oqat6Y3VHs?= =?us-ascii?Q?Aa1vsk0mvXcBh/Tm7Mgfyq3/1N/sDBAUrVK/mB/HSB/SzBqovvfJ/BKse8M9?= =?us-ascii?Q?UaT+s5g4QF0FctUDkJ+srJBCTTiJozwciGqv+vaFK0sFFd4XwFOVEgQP0n2A?= =?us-ascii?Q?JlDFcgOQOphI4pFlPzrGQoq0QLp4JIlbyw8/xEBCZClUE7qNDmqhBIv6dlmG?= =?us-ascii?Q?LmxLq/VbOFtlgcXIw6piQS5hs2DzKAlOBBaPo3pr893Q37G2rCDDPmBno2oR?= =?us-ascii?Q?Rzx2Sb0PK4ZjhY3oKMK5F/A48YR6lflXJFC8L8YDPZNK194XuTYOQljm1dwZ?= =?us-ascii?Q?Qts6CX1KoSkNmI6R0iUR45Jj+p0cUlroLIPCjbO/MFy+u7Zf+ZbZzooTmTHi?= =?us-ascii?Q?SuvmfE22YeHOBn5ptidPWz/FX8nnKwLQ6w4OziJHUJI6PDKw29IaknmsepWp?= =?us-ascii?Q?YNgfthyKFGbwuiTXwtKLN+ZI8NEYiW1APnyhBNV4g6WEpHFsLgPn5pD9A8sq?= =?us-ascii?Q?9+EZiN7jgr8ozQZFe7Wc7xMSRCCpMYDwy1KItodYAr1HOzRAJQznlKtoCJER?= =?us-ascii?Q?1XKpWkSrdae8fR9RX90nG9lBTUOZb/a2vwapFvsnRc4/s1a3bZxfYDzboCfj?= =?us-ascii?Q?OTM9U/yytabVMPr/K+U8/HNBTHYRVrb7GqC3r5FwrqmTlkt+t50sLUg2zNA8?= =?us-ascii?Q?FxtBKgpOVABuMbTy9nKU7bRiEBObVDjG4H3zKibfKwgbIJtUytpGByw4SURC?= =?us-ascii?Q?9dFsz0guCoHm7MThJ3ANBKE6Uud8JVpJiX6jte6KBYDf8uPdPTlezSv9JOAK?= =?us-ascii?Q?pbbUzfCwa4HR8p3+jrV40JkP7EA5FVmQR632W6o/bFGzCi26BwzM5oYrZoXD?= =?us-ascii?Q?qC62Gmt763P+6YeY8cFGE1Y7pPxt4Qqi/ajyL3q3OwYW7JJS5A+6buVcs1mr?= =?us-ascii?Q?7lAdNNTXS7ZE8vqtrz/+QKNJSwtjd0Cf954Oo23rnPLPgCXpODvD6D6v4rSk?= =?us-ascii?Q?ZmylyPFGnRNukXGWAsYu1eeQ?= x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_BYAPR02MB4613678609D6ED05586BAEE2D4909BYAPR02MB4613namp_" MIME-Version: 1.0 X-OriginatorOrg: stanford.edu X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: BYAPR02MB4613.namprd02.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 80177aa5-4199-4867-85bf-08d8e4230b48 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Mar 2021 00:17:23.5916 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 396573cb-f378-4b68-9bc8-15755c0c51f3 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: 5h2EI5/2H79cUrweMc1jSbnfUJRXNxQFomy6TBJVi0uZoOH455TJo6MAEHRVkyjM4C7UBnH/RQlq0jeAvVxuNg== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR02MB5400 x-proofpoint-stanford-dir: outbound X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-10_13:2021-03-10, 2021-03-10 signatures=0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-10_13:2021-03-10, 2021-03-10 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=100 impostorscore=0 lowpriorityscore=0 suspectscore=0 mlxlogscore=999 spamscore=0 clxscore=1015 malwarescore=0 mlxscore=0 priorityscore=1501 phishscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2103110000 Subject: Re: [dpdk-ci] [dpdk-users] Integration of DPDK into Bazel X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" --_000_BYAPR02MB4613678609D6ED05586BAEE2D4909BYAPR02MB4613namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Do you mean all components must be built inside bazel? >> Sort of. We have a project that is built on bazel. Now, we need to use t= he core functions of DPDK to replace the network primitives in our project,= so that we can improve the performance of our project. You are not able to call meson/ninja commands from bazel? >> I have found any examples using meson inside bazel. According to my unde= rstanding, Bazel and meson are two parallel building systems and I haven't = seen anyone could use them together. How do you do with other libraries? Does bazel usually reimplement what is = packaged with autotools? >> That is the reason why https://github.com/bazelment exists. If some libr= aries are popular and do not support bazel, then these guys will help gener= ate some modified version of these libraries, so that developers can integr= ate the library into bazel. It is not completely reimplementation, but it i= ndeed needs much extraction to adapt the previous library so that it can be= used in bazel. Unfortunately, these guys stop supporting DPDK atop bazel now. ________________________________ From: Thomas Monjalon Sent: Wednesday, March 10, 2021 4:06 PM To: Jinkun Geng Cc: Stephen Hemminger ; ci@dpdk.org ; users@dpdk.org Subject: Re: [dpdk-ci] [dpdk-users] Integration of DPDK into Bazel 11/03/2021 00:42, Jinkun Geng: > For any project using bazel, if we want to use DPDK, then we need to comp= ile DPDK stuff into bazel by ourselves. It is not a trivial thing and the b= azelment (https://github.com/bazelment/dpdk) guys have spent much effort ex= tracting the core files in DPDK and write the BUILD files for DPDK. But now= it seems they have stopped maintaining that repo since DPDK 16.04. Even in= that version, it has some runtime failure when we use DPDK in our bazel pr= oject. Sorry I don't know bazel. Do you mean all components must be built inside bazel? You are not able to call meson/ninja commands from bazel? How do you do with other libraries? Does bazel usually reimplement what is packaged with autotools? > ________________________________ From: Thomas Monjalon > 09/03/2021 05:11, Jinkun Geng: > > Too bad. :< > > Why is it too bad? > How the choice of an internal build system > can affect other projects? > > > From: Stephen Hemminger > > On Tue, 9 Mar 2021 01:32:16 +0000 > > Jinkun Geng wrote: > > > > > Hi, all. > > > Since bazel building system is becoming more and more popular, someti= mes we need to integrate DPDK library into a bazel project. However, it see= ms there is no much support for bazel from DPDK community. > > Why the DPDK community would support building with Bazel? > What is the benefit? > Bazel projects cannot just link with DPDK using pkg-config? > > > > > The only support at https://github.com/bazelment/dpdk has been outdat= ed. Based on our experience, it can only compile successfully with dpdk-16.= 04 (i.e. the bazel-16.04 branch). Now DPDK has developed to DPDK 21.02, but= the bazel support fails to catch up. > > > > > > It would be great if the experts in DPDK community can provide some p= ortable BUILD files to facilitate the integration of the newest DPDK into b= azel project (just like bazelment). After all, writing the bazel files can = be really challenging, especially if we do not have a very deep understandi= ng of the whole DPDK codes. > > > > > > Jinkun > > > > DPDK is on meson now. The core team is unlikely to change build systems= again. > > DPDK supports library standards for compiling, installing and linking. > What else is needed? --_000_BYAPR02MB4613678609D6ED05586BAEE2D4909BYAPR02MB4613namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Do you mean all components = must be built inside bazel?
>> Sort of. We have a= project that is built on bazel. Now, we need to use the core functions of = DPDK to replace the network primitives in our project, so that we can impro= ve the performance of our project.

You are not able to call me= son/ninja commands from bazel?
>> I have found any e= xamples using meson inside bazel. According to my understanding, Bazel and = meson are two parallel building systems and I haven't seen anyone could use= them together.

How do you do with other li= braries? Does bazel usually reimplement what is packaged with autotools?
>> That is the reason= why https://github.com/bazelment exists. If some libraries are popular and = do not support bazel, then these guys will help generate some modified vers= ion of these libraries, so that developers can integrate the library into b= azel. It is not completely reimplementation, but it indeed needs much extraction to adapt the previous library so that = it can be used in bazel.
Unfortunately, these guys s= top supporting DPDK atop bazel now.


From: Thomas Monjalon <t= homas@monjalon.net>
Sent: Wednesday, March 10, 2021 4:06 PM
To: Jinkun Geng <gjk1994@stanford.edu>
Cc: Stephen Hemminger <stephen@networkplumber.org>; ci@dpdk.or= g <ci@dpdk.org>; users@dpdk.org <users@dpdk.org>
Subject: Re: [dpdk-ci] [dpdk-users] Integration of DPDK into Bazel
 
11/03/2021 00:42, Jinkun Geng:
> For any project using bazel, if we want to use DPDK, then we need to c= ompile DPDK stuff into bazel by ourselves. It is not a trivial thing and th= e bazelment (https://github.c= om/bazelment/dpdk) guys have spent much effort extracting the core files in DPDK and write the BUILD files fo= r DPDK. But now it seems they have stopped maintaining that repo since DPDK= 16.04. Even in that version, it has some runtime failure when we use DPDK = in our bazel project.

Sorry I don't know bazel.
Do you mean all components must be built inside bazel?
You are not able to call meson/ninja commands from bazel?
How do you do with other libraries?
Does bazel usually reimplement what is packaged with autotools?


> ________________________________
From: Thomas Monjalon <thomas@monjalon.net>
> 09/03/2021 05:11, Jinkun Geng:
> > Too bad. :<
>
> Why is it too bad?
> How the choice of an internal build system
> can affect other projects?
>
>
> From: Stephen Hemminger <stephen@networkplumber.org>
> > On Tue, 9 Mar 2021 01:32:16 +0000
> > Jinkun Geng <gjk1994@stanford.edu> wrote:
> >
> > > Hi, all.
> > > Since bazel building system is becoming more and more popula= r, sometimes we need to integrate DPDK library into a bazel project. Howeve= r, it seems there is no much support for bazel from DPDK community.
>
> Why the DPDK community would support building with Bazel?
> What is the benefit?
> Bazel projects cannot just link with DPDK using pkg-config?
>
>
> > > The only support at https://github.com/bazelment/dpdk has been outdated. Based on our= experience, it can only compile successfully with dpdk-16.04 (i.e. the baz= el-16.04 branch). Now DPDK has developed to DPDK 21.02, but the bazel support fails to catch up.
> > >
> > > It would be great if the experts in DPDK community can provi= de some portable BUILD files to facilitate the integration of the newest DP= DK into bazel project (just like bazelment). After all, writing the bazel f= iles can be really challenging, especially if we do not have a very deep understanding of the whole DPDK codes.
> > >
> > > Jinkun
> >
> > DPDK is on meson now. The core team is unlikely to change build s= ystems again.
>
> DPDK supports library standards for compiling, installing and linking.=
> What else is needed?





--_000_BYAPR02MB4613678609D6ED05586BAEE2D4909BYAPR02MB4613namp_--