From: Stephen Hemminger <stephen@networkplumber•org>
To: David Hendel <david@silicom•co.il>
Cc: "netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"arnd@arndb•de" <arnd@arndb•de>, Anna Lukin <annal@silicom•co.il>,
"gregkh@linuxfoundation•org" <gregkh@linuxfoundation•org>
Subject: Re: Silicom bypass driver promote from staging
Date: Thu, 7 Aug 2014 09:55:45 -0700 [thread overview]
Message-ID: <20140807095545.2dd60024@haswell.linuxnetplumber.net> (raw)
In-Reply-To: <3BFAEADE799AF145974162DF00E013AF018F814DAB@exchange2010.silicom.local>
On Thu, 7 Aug 2014 09:26:54 +0000
David Hendel <david@silicom•co.il> wrote:
> Let me know how we can proceed with that. what should be the next step.
> -------------
> Theory of Operation:
> The Silicom Bypass Network Interface Cards (NICs) are network cards with paired ports (2 or 4).
> The pairs either act as a "wire" allowing the network packets to pass or insert the device in between the two ports. When paired with the on-board hardware watchdog or other failsafe, they provide high availability for the network in the face of software outages or maintenance.
>
> The software requirements are for a kernel level driver that interfaces with the bypass and watchdog, as well as for control software. User control can be either the provided standalone executable
> (/bin/bpctl) or the API exposed by the Silicom library.
The current driver uses a device specific /proc interface.
That API programming model will not likely be acceptable in a standard network driver.
Please consider doing something generic with netlink.
next prev parent reply other threads:[~2014-08-07 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BFAEADE799AF145974162DF00E013AF018F80FFCF@exchange2010.silicom.local>
[not found] ` <20140805150957.GC27303@kroah.com>
2014-08-07 9:26 ` Silicom bypass driver promote from staging David Hendel
2014-08-07 9:46 ` Jeff Kirsher
2014-08-07 16:55 ` Stephen Hemminger [this message]
2014-08-07 20:19 ` gregkh
2014-08-07 21:51 ` Francois Romieu
2014-09-27 6:54 ` David Hendel
2014-09-29 1:10 ` gregkh
2014-09-29 7:18 ` David Hendel
2014-09-29 7:18 ` David Hendel
2014-09-29 17:07 ` gregkh
2014-09-29 21:52 ` Francois Romieu
2014-09-29 7:22 ` David Hendel
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=20140807095545.2dd60024@haswell.linuxnetplumber.net \
--to=stephen@networkplumber$(echo .)org \
--cc=annal@silicom$(echo .)co.il \
--cc=arnd@arndb$(echo .)de \
--cc=david@silicom$(echo .)co.il \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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