From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0BF79C4321A for ; Tue, 11 Jun 2019 06:21:26 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 4C6292086A for ; Tue, 11 Jun 2019 06:21:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=Mellanox.com header.i=@Mellanox.com header.b="bfF8fkXE" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4C6292086A Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=mellanox.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A86971C264; Tue, 11 Jun 2019 08:21:23 +0200 (CEST) Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130080.outbound.protection.outlook.com [40.107.13.80]) by dpdk.org (Postfix) with ESMTP id AB31E1C25E for ; Tue, 11 Jun 2019 08:21:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Rf4Is5CDnO99jKJKql4IrURRnogAKCFI80EKHMNVzf4=; b=bfF8fkXES6Xo677oDnptyxbeV31UJo/cU7TZjSeDLnL8BavmRmAenR/p6acu0Ne08sLulJ9CpK/OvnllpMSGKlKcJHTmjNn1A6OWaYbYhvTunwQzrv22dmd6/GkIeEZiy/tkema96QojV02GAMVVvDyXeEtPClpNlPXoxcXLztI= Received: from AM0PR0502MB4019.eurprd05.prod.outlook.com (52.133.39.139) by AM0PR0502MB3985.eurprd05.prod.outlook.com (52.133.40.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.15; Tue, 11 Jun 2019 06:21:21 +0000 Received: from AM0PR0502MB4019.eurprd05.prod.outlook.com ([fe80::c5e8:f7ec:d77:5269]) by AM0PR0502MB4019.eurprd05.prod.outlook.com ([fe80::c5e8:f7ec:d77:5269%4]) with mapi id 15.20.1987.010; Tue, 11 Jun 2019 06:21:21 +0000 From: Matan Azrad To: Stephen Hemminger CC: "dev@dpdk.org" Thread-Topic: RFC - vdev_netvsc automatic blacklisting Thread-Index: AQHVGw9KGCRaWlcdwUWhNccsU0sDp6aWBGnA Date: Tue, 11 Jun 2019 06:21:21 +0000 Message-ID: References: <20190604125409.078adf75@hermes.lan> In-Reply-To: <20190604125409.078adf75@hermes.lan> Accept-Language: en-US, he-IL Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=matan@mellanox.com; x-originating-ip: [193.47.165.251] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: d59d49bc-84e0-4f6f-59bf-08d6ee350590 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:AM0PR0502MB3985; x-ms-traffictypediagnostic: AM0PR0502MB3985: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-forefront-prvs: 006546F32A x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(136003)(396003)(346002)(366004)(376002)(199004)(189003)(6116002)(3846002)(305945005)(4326008)(71200400001)(6916009)(71190400001)(53936002)(7736002)(74316002)(6246003)(229853002)(68736007)(316002)(6436002)(33656002)(5024004)(55016002)(256004)(73956011)(66066001)(8676002)(25786009)(8936002)(186003)(81156014)(81166006)(478600001)(99286004)(86362001)(7696005)(102836004)(2906002)(11346002)(26005)(52536014)(14454004)(446003)(6506007)(9686003)(66446008)(66476007)(5660300002)(66556008)(66946007)(476003)(64756008)(76116006)(486006)(76176011); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR0502MB3985; H:AM0PR0502MB4019.eurprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: mellanox.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: yaV0wbb+pChcvPfS1TQb+0COuZBafrbbsy+AMkPXH1LDcD+Nt5J++KcKy66Hmf9Bdt/NCbmVFQbBR3cSYnMe3Up4zjnBnnEvRZTrV9s9fQ+scTgz5qIuxxGGd5kM1MoPgBRoj9UYSTx0Y560viwiJPyUTRmyBhWNblCLNjErbOsL1N20PG2kpUBRNpWBYJMPZzt8ErY4u7wfaa+24vGf6YeTYXG0a6fIxeVFDh0eSwofwi+F11Lx5BQA6com09pWJHZEiMVNklf6Ha/3aQFyGozUFkuSQF1WCt+lQiRspXxON5b+EmIy2KajxeXLIN+HrSEputNkjcEwbUKssZHGOcpYe6bYwaj2F4I/Ukbd6N/ug7ImjJg9+Vp0puCOm1k2/Ktu8jXDful+EM3y9oM6ppCentzkBiua26CZwWDwOa0= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: Mellanox.com X-MS-Exchange-CrossTenant-Network-Message-Id: d59d49bc-84e0-4f6f-59bf-08d6ee350590 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jun 2019 06:21:21.2767 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: matan@mellanox.com X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR0502MB3985 Subject: Re: [dpdk-dev] RFC - vdev_netvsc automatic blacklisting X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Stephen From: Stephen Hemminger > When using DPDK on Azure it is common to have one non-DPDK interface. > If that non-DPDK interface is present vdev_netvsc correctly skip it. > But if the non-DPDK has accelerated networking the Mellanox driver will s= till > get associated with DPDK (and break connectivity). >=20 > The current process is to tell users to do whitelist or blacklist the PCI > device(s) not used for DPDK. But vdev_netvsc already is doing a lot of lo= oking > at devices and VF devices. >=20 > Could vdev_netvsc just do this automatically by setting devargs for the V= F to > blacklist? There is way to blacklist a device by setting it a rout\IP\IPv6, from the V= DEV_NETVSC doc: "Not specifying either iface or mac makes this driver attach itself to all = unrouted NetVSC interfaces found on the system. Specifying the device makes= this driver attach itself to the device regardless the device routes." So, we are expecting that used VFs will be with a rout and DPDK VFs will no= t be with a rout. Doesn't it enough? Matan