From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <prvs=101199d020=jerinj@marvell.com>
Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com
 [67.231.148.174]) by dpdk.org (Postfix) with ESMTP id 372E71B93F
 for <dev@dpdk.org>; Thu, 18 Apr 2019 07:57:22 +0200 (CEST)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1])
 by mx0a-0016f401.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id
 x3I5okac025907; Wed, 17 Apr 2019 22:57:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com;
 h=from : to : cc :
 subject : date : message-id : references : in-reply-to : content-type :
 content-transfer-encoding : mime-version; s=pfpt0818;
 bh=Mtdv0KR7EWJQ1y7F2SMS/FKRAGMWzfOKXrs5xLuw7t4=;
 b=r2To+cOU48n0NYjY1JLsioIzfaQQkGNYaWRiYDoTOzNrRKyHzbovc8umZ+KNab+Io2Ri
 KgaimiyrXNoPVIlZPukxpwk3N2WAwttsOBQdTPpYqKbyik5hEpF4/Vx5cmQyF9q+mKXR
 9KlivLTPNCcovMiENigqj/s8g2eg1M09oXT1FSZ/gIRSgGT0zbPY5iL/1/NVBNgQttZ/
 h5qYAudO4JDOZSgwnBT4ruV6qnK12QiAlteHmHwBo3/ggafShf0rFDh+vHen01AuNVBc
 JvidNprILRNgJmmgNvJNHRchBwaVAT2N8kEXwEvf8BCxpyoG+iOmAL8WYxOLR2WWQmoI LA== 
Received: from sc-exch02.marvell.com ([199.233.58.182])
 by mx0a-0016f401.pphosted.com with ESMTP id 2rx3mpkt7e-1
 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT);
 Wed, 17 Apr 2019 22:57:01 -0700
Received: from SC-EXCH01.marvell.com (10.93.176.81) by SC-EXCH02.marvell.com
 (10.93.176.82) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 17 Apr
 2019 22:57:01 -0700
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (104.47.36.58) by
 SC-EXCH01.marvell.com (10.93.176.81) with Microsoft SMTP Server
 (TLS) id
 15.0.1367.3 via Frontend Transport; Wed, 17 Apr 2019 22:57:01 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=marvell.onmicrosoft.com; s=selector1-marvell-com;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=Mtdv0KR7EWJQ1y7F2SMS/FKRAGMWzfOKXrs5xLuw7t4=;
 b=MzsHUJk0JJ1sifONwgkE3QNO0Ws5E3dgojHHQtRMC9MuJ8FORtCWxlWA9rC3eAIm6zjISzQyuTZ341vKiGN1g9PQVC6YanEfqsnvV/3XZHAVv1NX1nX+XBzzZsQcAQG27kHl+0VNzciiqhTFo0zHKtm7DRHbMyhalbevgWcRTnc=
Received: from BYAPR18MB2424.namprd18.prod.outlook.com (20.179.91.149) by
 BYAPR18MB2533.namprd18.prod.outlook.com (20.179.93.29) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.1813.12; Thu, 18 Apr 2019 05:56:55 +0000
Received: from BYAPR18MB2424.namprd18.prod.outlook.com
 ([fe80::6dd3:c056:b23b:ab4e]) by BYAPR18MB2424.namprd18.prod.outlook.com
 ([fe80::6dd3:c056:b23b:ab4e%7]) with mapi id 15.20.1813.011; Thu, 18 Apr 2019
 05:56:55 +0000
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Stephen Hemminger <stephen@networkplumber.org>
CC: Bruce Richardson <bruce.richardson@intel.com>, Honnappa Nagarahalli
 <Honnappa.Nagarahalli@arm.com>, "dev@dpdk.org" <dev@dpdk.org>, "Ananyev,
 Konstantin" <konstantin.ananyev@intel.com>, "thomas@monjalon.net"
 <thomas@monjalon.net>, Ray Kinsella <mdr@ashroe.eu>, nd <nd@arm.com>
Thread-Topic: [EXT] Re: [dpdk-dev] ABI and inline functions
Thread-Index: AdT03C2s3ZB+VIuxS0mLCJ+6mgHcvgAHH6YAABKU0YAAAuGKAAAXFGRw
Date: Thu, 18 Apr 2019 05:56:55 +0000
Message-ID: <BYAPR18MB24241F838D93162AE0F2F559C8260@BYAPR18MB2424.namprd18.prod.outlook.com>
References: <VE1PR08MB5149D3D24CD4F903FCFFE14798250@VE1PR08MB5149.eurprd08.prod.outlook.com>
 <20190417083637.GB1890@bricha3-MOBL.ger.corp.intel.com>
 <BYAPR18MB2424FB7B26FFE737C4871561C8250@BYAPR18MB2424.namprd18.prod.outlook.com>
 <20190417115110.5cb70832@hermes.lan>
In-Reply-To: <20190417115110.5cb70832@hermes.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2401:4900:315b:bc23:b844:e415:f584:5eb9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4ca893d9-a8fc-484a-7af8-08d6c3c2a9cf
x-microsoft-antispam: BCL:0; PCL:0;
 RULEID:(2390118)(7020095)(4652040)(8989299)(5600141)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020);
 SRVR:BYAPR18MB2533; 
x-ms-traffictypediagnostic: BYAPR18MB2533:
x-microsoft-antispam-prvs: <BYAPR18MB2533AF3C57E97DB07F1A54E9C8260@BYAPR18MB2533.namprd18.prod.outlook.com>
x-forefront-prvs: 0011612A55
x-forefront-antispam-report: SFV:NSPM;
 SFS:(10009020)(39860400002)(136003)(346002)(376002)(396003)(366004)(52314003)(13464003)(189003)(199004)(52536014)(55016002)(93886005)(478600001)(5660300002)(9686003)(7696005)(33656002)(476003)(99286004)(46003)(186003)(6916009)(25786009)(14454004)(76176011)(256004)(14444005)(486006)(2906002)(53936002)(8676002)(68736007)(97736004)(74316002)(4326008)(81166006)(81156014)(7736002)(102836004)(6246003)(53546011)(6506007)(86362001)(316002)(11346002)(8936002)(229853002)(6436002)(446003)(71200400001)(305945005)(71190400001)(54906003)(6116002);
 DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR18MB2533;
 H:BYAPR18MB2424.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en;
 PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: marvell.com does not designate
 permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: DEppay3kaGY7hraPB99eXySVBWFn8oRkqwWqmz+P23TcDCzcVxFX0vLuRp8agOjmmApU/wmbvMPBk2wJSF7JI9znfJJp1INJA1fwW5tfHjkg4af8kL9Be2SuaVdw7p3dsP09kWMu4HjFTtaf4eXIGNLHendLPfA8HIJlfQdeLOBT1ft4S07jogGgnzQD9KgOrE++ytW31FfrUEzkACjiWZtYXZ6LZygzgdqGDjiVTxzq96R17O3Fx5ivJHpblQBOpakq04kskkEfLZZZn19riE7Qx7aTuem+OvkVpXNdE5vZB1kiWIKVrA7GPBj75WZZLZSWv2bmenyPFP4a1goa90ggIL6yUz8WgvVzt/jeB2hNkB4YF1TDB9HrZnUabUz45mGfh0rt4/eVZCrOJyOS2dh1T4Jr5jEub18IW4pAER4=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4ca893d9-a8fc-484a-7af8-08d6c3c2a9cf
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Apr 2019 05:56:55.7661 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 70e1fb47-1155-421d-87fc-2e58f638b6e0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR18MB2533
X-OriginatorOrg: marvell.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, ,
 definitions=2019-04-18_03:, , signatures=0
Subject: Re: [dpdk-dev] [EXT] Re:  ABI and inline functions
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2019 05:57:22 -0000


> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Thursday, April 18, 2019 12:21 AM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> Cc: Bruce Richardson <bruce.richardson@intel.com>; Honnappa Nagarahalli
> <Honnappa.Nagarahalli@arm.com>; dev@dpdk.org; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>; thomas@monjalon.net; Ray Kinsella
> <mdr@ashroe.eu>; nd <nd@arm.com>
> Subject: [EXT] Re: [dpdk-dev] ABI and inline functions
> > I would value ABI compatibility much higher than API compatibility.
> > > If someone is recompiling the application anyway, making a couple of
> > > small changes (large rework is obviously a different issue) to the
> > > code should not be a massive issue, I hope. On the other hand, ABI
> > > compatibility is needed to allow seamless update from one version to
> > > another, and it's that ABI compatiblity that allows distro's to pick =
up our
> latest and greatest versions.
> >
> > IMO, We have two primary use case for DPDK
> >
> > 1) NFV kind of use case 	where the application needs to run on multiple
> platform
> > without recompiling it.
> > 2) Fixed appliance use case where embed SoC like Intel Denverton or
> > ARM64 integrated Controller used. For fixed appliance use case, end
> > user care more of performance than ABI compatibility as it easy to
> > recompile the end user application vs the cost of hitting performance i=
mpact.
>=20
> Nobody cares about compatiablity until they have to the first security up=
date.

For fixed appliance case, The update(FW update) will be  a single blob whic=
h
Include all the components. So they can back port the security fix and reco=
mpile
the sw as needed.

The very similar category  is DPDK running in smart NICs(Runs as FW in PCIe=
 EP device).



>=20

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by dpdk.space (Postfix) with ESMTP id EABB7A00E6
	for <public@inbox.dpdk.org>; Thu, 18 Apr 2019 07:57:24 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 146631B941;
	Thu, 18 Apr 2019 07:57:23 +0200 (CEST)
Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com
 [67.231.148.174]) by dpdk.org (Postfix) with ESMTP id 372E71B93F
 for <dev@dpdk.org>; Thu, 18 Apr 2019 07:57:22 +0200 (CEST)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1])
 by mx0a-0016f401.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id
 x3I5okac025907; Wed, 17 Apr 2019 22:57:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com;
 h=from : to : cc :
 subject : date : message-id : references : in-reply-to : content-type :
 content-transfer-encoding : mime-version; s=pfpt0818;
 bh=Mtdv0KR7EWJQ1y7F2SMS/FKRAGMWzfOKXrs5xLuw7t4=;
 b=r2To+cOU48n0NYjY1JLsioIzfaQQkGNYaWRiYDoTOzNrRKyHzbovc8umZ+KNab+Io2Ri
 KgaimiyrXNoPVIlZPukxpwk3N2WAwttsOBQdTPpYqKbyik5hEpF4/Vx5cmQyF9q+mKXR
 9KlivLTPNCcovMiENigqj/s8g2eg1M09oXT1FSZ/gIRSgGT0zbPY5iL/1/NVBNgQttZ/
 h5qYAudO4JDOZSgwnBT4ruV6qnK12QiAlteHmHwBo3/ggafShf0rFDh+vHen01AuNVBc
 JvidNprILRNgJmmgNvJNHRchBwaVAT2N8kEXwEvf8BCxpyoG+iOmAL8WYxOLR2WWQmoI LA== 
Received: from sc-exch02.marvell.com ([199.233.58.182])
 by mx0a-0016f401.pphosted.com with ESMTP id 2rx3mpkt7e-1
 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT);
 Wed, 17 Apr 2019 22:57:01 -0700
Received: from SC-EXCH01.marvell.com (10.93.176.81) by SC-EXCH02.marvell.com
 (10.93.176.82) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 17 Apr
 2019 22:57:01 -0700
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (104.47.36.58) by
 SC-EXCH01.marvell.com (10.93.176.81) with Microsoft SMTP Server
 (TLS) id
 15.0.1367.3 via Frontend Transport; Wed, 17 Apr 2019 22:57:01 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=marvell.onmicrosoft.com; s=selector1-marvell-com;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=Mtdv0KR7EWJQ1y7F2SMS/FKRAGMWzfOKXrs5xLuw7t4=;
 b=MzsHUJk0JJ1sifONwgkE3QNO0Ws5E3dgojHHQtRMC9MuJ8FORtCWxlWA9rC3eAIm6zjISzQyuTZ341vKiGN1g9PQVC6YanEfqsnvV/3XZHAVv1NX1nX+XBzzZsQcAQG27kHl+0VNzciiqhTFo0zHKtm7DRHbMyhalbevgWcRTnc=
Received: from BYAPR18MB2424.namprd18.prod.outlook.com (20.179.91.149) by
 BYAPR18MB2533.namprd18.prod.outlook.com (20.179.93.29) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.1813.12; Thu, 18 Apr 2019 05:56:55 +0000
Received: from BYAPR18MB2424.namprd18.prod.outlook.com
 ([fe80::6dd3:c056:b23b:ab4e]) by BYAPR18MB2424.namprd18.prod.outlook.com
 ([fe80::6dd3:c056:b23b:ab4e%7]) with mapi id 15.20.1813.011; Thu, 18 Apr 2019
 05:56:55 +0000
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Stephen Hemminger <stephen@networkplumber.org>
CC: Bruce Richardson <bruce.richardson@intel.com>, Honnappa Nagarahalli
 <Honnappa.Nagarahalli@arm.com>, "dev@dpdk.org" <dev@dpdk.org>, "Ananyev,
 Konstantin" <konstantin.ananyev@intel.com>, "thomas@monjalon.net"
 <thomas@monjalon.net>, Ray Kinsella <mdr@ashroe.eu>, nd <nd@arm.com>
Thread-Topic: [EXT] Re: [dpdk-dev] ABI and inline functions
Thread-Index: AdT03C2s3ZB+VIuxS0mLCJ+6mgHcvgAHH6YAABKU0YAAAuGKAAAXFGRw
Date: Thu, 18 Apr 2019 05:56:55 +0000
Message-ID:
 <BYAPR18MB24241F838D93162AE0F2F559C8260@BYAPR18MB2424.namprd18.prod.outlook.com>
References: <VE1PR08MB5149D3D24CD4F903FCFFE14798250@VE1PR08MB5149.eurprd08.prod.outlook.com>
 <20190417083637.GB1890@bricha3-MOBL.ger.corp.intel.com>
 <BYAPR18MB2424FB7B26FFE737C4871561C8250@BYAPR18MB2424.namprd18.prod.outlook.com>
 <20190417115110.5cb70832@hermes.lan>
In-Reply-To: <20190417115110.5cb70832@hermes.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2401:4900:315b:bc23:b844:e415:f584:5eb9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4ca893d9-a8fc-484a-7af8-08d6c3c2a9cf
x-microsoft-antispam: BCL:0; PCL:0;
 RULEID:(2390118)(7020095)(4652040)(8989299)(5600141)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020);
 SRVR:BYAPR18MB2533; 
x-ms-traffictypediagnostic: BYAPR18MB2533:
x-microsoft-antispam-prvs: <BYAPR18MB2533AF3C57E97DB07F1A54E9C8260@BYAPR18MB2533.namprd18.prod.outlook.com>
x-forefront-prvs: 0011612A55
x-forefront-antispam-report: SFV:NSPM;
 SFS:(10009020)(39860400002)(136003)(346002)(376002)(396003)(366004)(52314003)(13464003)(189003)(199004)(52536014)(55016002)(93886005)(478600001)(5660300002)(9686003)(7696005)(33656002)(476003)(99286004)(46003)(186003)(6916009)(25786009)(14454004)(76176011)(256004)(14444005)(486006)(2906002)(53936002)(8676002)(68736007)(97736004)(74316002)(4326008)(81166006)(81156014)(7736002)(102836004)(6246003)(53546011)(6506007)(86362001)(316002)(11346002)(8936002)(229853002)(6436002)(446003)(71200400001)(305945005)(71190400001)(54906003)(6116002);
 DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR18MB2533;
 H:BYAPR18MB2424.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en;
 PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: marvell.com does not designate
 permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: DEppay3kaGY7hraPB99eXySVBWFn8oRkqwWqmz+P23TcDCzcVxFX0vLuRp8agOjmmApU/wmbvMPBk2wJSF7JI9znfJJp1INJA1fwW5tfHjkg4af8kL9Be2SuaVdw7p3dsP09kWMu4HjFTtaf4eXIGNLHendLPfA8HIJlfQdeLOBT1ft4S07jogGgnzQD9KgOrE++ytW31FfrUEzkACjiWZtYXZ6LZygzgdqGDjiVTxzq96R17O3Fx5ivJHpblQBOpakq04kskkEfLZZZn19riE7Qx7aTuem+OvkVpXNdE5vZB1kiWIKVrA7GPBj75WZZLZSWv2bmenyPFP4a1goa90ggIL6yUz8WgvVzt/jeB2hNkB4YF1TDB9HrZnUabUz45mGfh0rt4/eVZCrOJyOS2dh1T4Jr5jEub18IW4pAER4=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4ca893d9-a8fc-484a-7af8-08d6c3c2a9cf
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Apr 2019 05:56:55.7661 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 70e1fb47-1155-421d-87fc-2e58f638b6e0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR18MB2533
X-OriginatorOrg: marvell.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, ,
 definitions=2019-04-18_03:, , signatures=0
Subject: Re: [dpdk-dev] [EXT] Re:  ABI and inline functions
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>
Message-ID: <20190418055655._X3HHJkTHTOhrP-AxAUPiInsp8ZCMZ7r8rgPc0kKIz8@z>


> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Thursday, April 18, 2019 12:21 AM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> Cc: Bruce Richardson <bruce.richardson@intel.com>; Honnappa Nagarahalli
> <Honnappa.Nagarahalli@arm.com>; dev@dpdk.org; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>; thomas@monjalon.net; Ray Kinsella
> <mdr@ashroe.eu>; nd <nd@arm.com>
> Subject: [EXT] Re: [dpdk-dev] ABI and inline functions
> > I would value ABI compatibility much higher than API compatibility.
> > > If someone is recompiling the application anyway, making a couple of
> > > small changes (large rework is obviously a different issue) to the
> > > code should not be a massive issue, I hope. On the other hand, ABI
> > > compatibility is needed to allow seamless update from one version to
> > > another, and it's that ABI compatiblity that allows distro's to pick =
up our
> latest and greatest versions.
> >
> > IMO, We have two primary use case for DPDK
> >
> > 1) NFV kind of use case 	where the application needs to run on multiple
> platform
> > without recompiling it.
> > 2) Fixed appliance use case where embed SoC like Intel Denverton or
> > ARM64 integrated Controller used. For fixed appliance use case, end
> > user care more of performance than ABI compatibility as it easy to
> > recompile the end user application vs the cost of hitting performance i=
mpact.
>=20
> Nobody cares about compatiablity until they have to the first security up=
date.

For fixed appliance case, The update(FW update) will be  a single blob whic=
h
Include all the components. So they can back port the security fix and reco=
mpile
the sw as needed.

The very similar category  is DPDK running in smart NICs(Runs as FW in PCIe=
 EP device).



>=20