From: Jean-Christophe BEGUE <jean-christophe.begue@fraudbuster.mobi>
To: dev@dpdk.org
Subject: [dpdk-dev] A couple question before starting to work on a Silicom NIC-Bypass driver implementation
Date: Fri, 07 Sep 2018 18:06:09 +0200 [thread overview]
Message-ID: <1536336369.5517.3@smtp.fraudbuster.mobi> (raw)
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!
reply other threads:[~2018-09-07 16:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1536336369.5517.3@smtp.fraudbuster.mobi \
--to=jean-christophe.begue@fraudbuster.mobi \
--cc=dev@dpdk.org \
/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).