From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jean-christophe.begue@fraudbuster.mobi>
Received: from varys.fraudbuster.mobi (varys.fraudbuster.mobi [195.154.36.198])
 by dpdk.org (Postfix) with ESMTP id 56B852BEA
 for <dev@dpdk.org>; Fri,  7 Sep 2018 18:06:13 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by varys.fraudbuster.mobi (Postfix) with ESMTP id 30A46D69E4
 for <dev@dpdk.org>; Fri,  7 Sep 2018 18:06:13 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fraudbuster.mobi;
 s=mail; t=1536336373;
 bh=OaOD0g+A9M8Wq1Qi7ee4G7sz4J4jeV/KgomBJ2rrZBI=;
 h=Date:From:Subject:To:From;
 b=RnFhMDHu1lYXgjko8lwLdy/cjJ3tZMIb26RlU7jF0h8Q1yaMk0766uVd9dkgQUzjp
 Ln3RrXWnAfDlrxEfEH9JoBaR6CnKtgIasN2zowXPbhlMFbConDa8YQf9HTt3FumchL
 Y5TMPmMILdY+yk9fi7HlRgS0nS5QW9zURHWHmmpw=
X-Virus-Scanned: scanned at varys.fraudbuster.mobi
Received: from [127.0.0.1] ([127.0.0.1])
 by localhost (varys.fraudbuster.mobi [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id zzsRLrqMJQAC for <dev@dpdk.org>;
 Fri,  7 Sep 2018 18:06:13 +0200 (CEST)
Received: from [172.16.61.31] (LNeuilly-656-1-133-210.w80-11.abo.wanadoo.fr
 [80.11.182.210])
 by varys.fraudbuster.mobi (Postfix) with ESMTPSA id 3C735D69BB
 for <dev@dpdk.org>; Fri,  7 Sep 2018 18:06:11 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=fraudbuster.mobi;
 s=mail; t=1536336373;
 bh=Nzb8iGVAyFlvZ3aVqRGmOsobgC4nOVhk/DokpTldQs4=;
 h=Date:From:Subject:To:From;
 b=JXFXpjunjs7rVNifCXrybG4DoXu9zfHAyzRyh3GSGYoKgXaKgZBvsP8Qi6chkK/HC
 B4VQgu/NHhQ2NJHczlgCOD9x4llWR1Q8kaG9lIYMQ1RcKS43OT2OzqfWOpkbgTXZgl
 Plu3ROLSB4JDFrHAX6SJXEL4o47uGQQTpVwyN9a0=
Authentication-Results: varys.fraudbuster.mobi;
 dmarc=fail header.from=fraudbuster.mobi
Date: Fri, 07 Sep 2018 18:06:09 +0200
From: Jean-Christophe BEGUE <jean-christophe.begue@fraudbuster.mobi>
To: dev@dpdk.org
Message-Id: <1536336369.5517.3@smtp.fraudbuster.mobi>
X-Mailer: geary/0.12-dev
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] A couple question before starting to work on a Silicom
 NIC-Bypass driver implementation
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: Fri, 07 Sep 2018 16:06:13 -0000

Hello everyone,

Here at FraudBuster we really need a NIC-Bypass feature to be 
integrated in our products.

We've been able to use the Silicom boards we can find here: 
https://bit.ly/2NrIK7z .
Unfortunately the only driver Silicom seems to support is written for 
kernel-space bound interfaces: you need your interface to have an 
`interface index`  assigned in the kernel, which I beleive is not a 
common thing in the DPDK bound way of accessing hardware.

We were able to get a functional driver from Silicom's module with a 
quick and dirty hack. But we would be very interested in writing a 
DPDK-integrated driver has the one implemented in 
`drivers/net/ixgbe/ixgbe_bypass.c`. It seems to share similarities in 
hardware implementation, in particular the I2C bit-banging control via 
ESDP.

We would like to start with the PE210G2BPI9, a Dual Port Fiber 10G, 
82599ES Based.

But first, as I am totally new to the DPDK world, I have a couple of 
question:

How would the community welcome this feature ? Would it be useful for 
some DPDK users ?

Would some people agree to mentor my work, review and give me advice. 
Helping me to integrate well into the project architecture and reach 
the required code quality required to be merged ?

Thank you!