netdev - Re: [PATCH net-next] qed: Add Light L2 [ll2] infrastructure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20160615.221701.587394586942508875.davem@davemloft.net>
Date:	Wed, 15 Jun 2016 22:17:01 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	Yuval.Mintz@...gic.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] qed: Add Light L2 [ll2] infrastructure

From: Yuval Mintz <Yuval.Mintz@...gic.com>
Date: Wed, 15 Jun 2016 13:22:37 +0300

> The qed driver will allow support for several drivers other than
> qede, and each of said protocol drivers will require some sort of
> L2-like ability to send and receive traffic -
> the common use-case would be for control traffic specific for the
> protocol that needs to reach user/kernel tools, although other cases
> exist as well [some of which are for internal use by firmware].

You have to describe in more detail who these users will be.

Actually, you are required to submit a use case along with any new
facility and set of interfaces like this.

Otherwise it is impossible to review the facility and make sure it
does what it is supposed to do, and is designed well for it's intended
use case.