linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Yuval Avnery <yuvalav@mellanox.com>,
	Jiri Pirko <jiri@mellanox.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Gospodarek <andy@greyhouse.net>
Subject: Re: [PATCH net-next] netdevsim: Add max_vfs to bus_dev
Date: Thu, 12 Dec 2019 20:47:32 +0200	[thread overview]
Message-ID: <20191212184732.GA570918@splinter> (raw)
In-Reply-To: <20191212102517.602a8a5d@cakuba.netronome.com>

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.

  reply	other threads:[~2019-12-12 18:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11  2:58 [PATCH net-next] netdevsim: Add max_vfs to bus_dev Yuval Avnery
2019-12-11 17:58 ` Jakub Kicinski
2019-12-11 18:19   ` Yuval Avnery
2019-12-11 19:15     ` Jakub Kicinski
2019-12-11 19:57       ` Yuval Avnery
2019-12-11 22:24         ` Jakub Kicinski
2019-12-11 23:25           ` Yuval Avnery
2019-12-11 23:49             ` Jakub Kicinski
2019-12-12  5:11               ` Yuval Avnery
2019-12-12 18:25                 ` Jakub Kicinski
2019-12-12 18:47                   ` Ido Schimmel [this message]
2019-12-13  1:37                     ` Jakub Kicinski
2019-12-12 20:44                   ` Yuval Avnery
2019-12-13  1:54                     ` Jakub Kicinski
2019-12-13  3:21                       ` Yuval Avnery
2019-12-13 18:08                         ` Jakub Kicinski
2019-12-13 20:05                           ` Yuval Avnery
2019-12-16 20:44                             ` Jakub Kicinski
2019-12-16 22:52                               ` Yuval Avnery
2019-12-17 19:06                                 ` Yuval Avnery

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191212184732.GA570918@splinter \
    --to=idosch@idosch.org \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=jakub.kicinski@netronome.com \
    --cc=jiri@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yuvalav@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).