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=-2.2 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no 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 0C353C43603 for ; Thu, 12 Dec 2019 18:47:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D3157206C3 for ; Thu, 12 Dec 2019 18:47:37 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="VHyI13Hr" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730470AbfLLSrg (ORCPT ); Thu, 12 Dec 2019 13:47:36 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:45851 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730258AbfLLSrg (ORCPT ); Thu, 12 Dec 2019 13:47:36 -0500 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 36169220DD; Thu, 12 Dec 2019 13:47:35 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 12 Dec 2019 13:47:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=4mxdiD QsfZD57JRu05aHGqyvwaIJ8QTGQZI90Fgydd4=; b=VHyI13HrTGZaW29m3NPvPp QYnyqv1yxXQqfY7S65bQ1P8D+a1s4FBvXARJxdoqRT6NY+CPbtG/eXPNSmCJKB1j zNsUMC9OUmMu5gurOWxl0LffUQCVGXiRQwS4PzI94O+wQg8fO+7iqOcXfSnQQEuP sBpePNNhk/W7ijzo6LgE/eMwnB9WXP5N4/Xeh4CGNNFC4teXNPlbknopT1a1jxT6 3hG5LfI/PFCFpBsVUFiYhgvF/vW82hrxy1B8mdR6X8UlH5iTTHp0Xy3wb/9zyZSz 2KI8qoa58NKLLWkegCDzubVbobEKy8AQ4ndv+IcjQz7zOSwqA1MUBfjv5De1V/aQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeljedguddukecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefkugho ucfutghhihhmmhgvlhcuoehiughoshgthhesihguohhstghhrdhorhhgqeenucfkphepud elfedrgeejrdduieehrddvhedunecurfgrrhgrmhepmhgrihhlfhhrohhmpehiughoshgt hhesihguohhstghhrdhorhhgnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from localhost (unknown [193.47.165.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 5ABE13060134; Thu, 12 Dec 2019 13:47:34 -0500 (EST) Date: Thu, 12 Dec 2019 20:47:32 +0200 From: Ido Schimmel To: Jakub Kicinski Cc: Yuval Avnery , Jiri Pirko , "davem@davemloft.net" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Andy Gospodarek Subject: Re: [PATCH net-next] netdevsim: Add max_vfs to bus_dev Message-ID: <20191212184732.GA570918@splinter> References: <1576033133-18845-1-git-send-email-yuvalav@mellanox.com> <20191211095854.6cd860f1@cakuba.netronome.com> <20191211111537.416bf078@cakuba.netronome.com> <20191211142401.742189cf@cakuba.netronome.com> <20191211154952.50109494@cakuba.netronome.com> <20191212102517.602a8a5d@cakuba.netronome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191212102517.602a8a5d@cakuba.netronome.com> User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 12, 2019 at 10:25:17AM -0800, Jakub Kicinski wrote: > I'd like to see netdevsim to also serve as sort of a reference model > for device behaviour. Vendors who are not first to implement a feature > always complain that there is no documentation on how things should > work. +1 I have a patch set that adds FIB offload implementation to netdevsim and a gazillion of test cases that I share between netdevsim and mlxsw. Can be used by more drivers when they land. It's also very convenient for fuzzing now that syzkaller supports netdevsim instances thanks to Jiri. I've been running syzkaller for a few weeks now to test the FIB implementation.