All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: pjonnala@broadcom.com
Cc: f.fainelli@gmail.com, netdev@vger.kernel.org, sfeldma@gmail.com,
	jiri@resnulli.us, nikolay@cumulusnetworks.com,
	idosch@mellanox.com, gospo@cumulusnetworks.com
Subject: Re: [PATCH] bonding: Offloading bonds to hardware
Date: Mon, 16 Nov 2015 01:54:24 -0500 (EST)	[thread overview]
Message-ID: <20151116.015424.1232779372973422034.davem@davemloft.net> (raw)
In-Reply-To: <77EF4405DD4BB54AACCE7DB593DF6A9AA09053@SJEXCHMB14.corp.ad.broadcom.com>

From: Premkumar Jonnala <pjonnala@broadcom.com>
Date: Mon, 16 Nov 2015 06:49:49 +0000

>> Thank you for the feedback David.  I am currently handling/implementing
>> these notifications in a custom (closed source) driver.  I will update the diff
>> with an actual demo of the handler, and resend the diffs.
> 
> Clarification: When I say a "closed source" driver, I was implying a closed-source
> user-level application that programs hardware.

This makes no sense at all.

You're adding kernel level hooks that some kernel level driver,
upstream, has to make use of.

A "closed source" user level component has no bearing whatsoever
upon this.

I want to see a kernel driver that's in the upstream tree now,
implementing support for the new facility.

Period.

  reply	other threads:[~2015-11-16  6:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 16:02 [PATCH] bonding: Offloading bonds to hardware Premkumar Jonnala
2015-11-12 17:08 ` Andrew Lunn
2015-11-14  9:40   ` Jiri Pirko
2015-11-13 18:38 ` Florian Fainelli
2015-11-13 19:10   ` David Miller
2015-11-16  6:12     ` Premkumar Jonnala
2015-11-16  6:51       ` David Miller
2015-11-16  6:49     ` Premkumar Jonnala
2015-11-16  6:54       ` David Miller [this message]
2015-11-16  6:10   ` Premkumar Jonnala
2015-11-13 21:11 ` Andrew Lunn
2015-11-16  6:15   ` Premkumar Jonnala
2015-11-14  9:39 ` Jiri Pirko
2015-11-15  5:51   ` John Fastabend
2015-11-15  9:01     ` Jiri Pirko
2015-11-16 16:24       ` John Fastabend
2015-11-16  6:48   ` Premkumar Jonnala
2015-11-16  7:46     ` Jiri Pirko

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=20151116.015424.1232779372973422034.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=gospo@cumulusnetworks.com \
    --cc=idosch@mellanox.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=pjonnala@broadcom.com \
    --cc=sfeldma@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.