Netdev List
 help / color / mirror / Atom feed
From: John Fastabend <john.r.fastabend@intel.com>
To: Jay Vosburgh <fubar@us.ibm.com>,
	Anirban Chakraborty <anirban.chakraborty@qlogic.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	Dept_NX_Linux_NIC_Driver@qlogic.com
Subject: Re: [PATCH net-next] bonding: Support for multi function NIC devices
Date: Sun, 15 Jul 2012 21:39:45 -0700	[thread overview]
Message-ID: <50039B11.1010006@intel.com> (raw)
In-Reply-To: <20657.1342402819@death.nxdomain>

On 7/15/2012 6:40 PM, Jay Vosburgh wrote:
> Anirban Chakraborty <anirban.chakraborty@qlogic.com> wrote:
>
>> From: Anirban Chakraborty <anirban.chakraborty@qlogic.com>
>>
>> Add support to disable bonding of interfaces belonging to the same physical port. In
>> case of SRIOV or NIC partition mode, a single port of the adapter can have multiple
>> NIC functions. While bonding such interfaces, it is ensured that the NIC functions
>> belonging to the same physical port are not bonded together.
>>
>> Signed-off-by: Anirban Chakraborty <anirban.chakraborty@qlogic.com>
>> ---
>> Documentation/networking/ifenslave.c |  208 +++++++++++++++++++++++++++++++++-
>> 1 files changed, 207 insertions(+), 1 deletions(-)
>>
>> diff --git a/Documentation/networking/ifenslave.c b/Documentation/networking/ifenslave.c
>> index ac5debb..a0bdab9 100644
>> --- a/Documentation/networking/ifenslave.c
>> +++ b/Documentation/networking/ifenslave.c
>> @@ -92,9 +92,14 @@
>>   *    - 2003/12/01 - Shmulik Hen <shmulik.hen at intel dot com>
>>   *	 - Code cleanup and style changes
>>   *	   set version to 1.1.0
>> + *
>> + *    - 2012/07/15 - Anirban Chakraborty <anirban.chakraborty at qlogic dot com>
>> + *	 - Added support to disable bonding interfaces belonging to the
>> + *	   same physical port.
>> + *	   set version to 1.1.1
>
> 	This patch is all implemented within the ifenslave user space
> program, which, to my knowledge, is not currently used by any major
> distro to configure bonding.
>
> 	The configuration for bonding is typically performed by packages
> such as initscripts or sysconfig, and this functionality would likely
> need to go there.
>
> 	The only real use for ifenslave.c is on kernels without sysfs
> compiled in.
>
> 	-J
>

Also I'm not sure we need to explicitly block this.  It is clear from 
looking at 'ip' output what the topology is. And in the SR-IOV
case would this still work if the functions are direct assigned? How
about if I try to bond two stacked devices that are on the same
physical link. In both case iirc the bus info wont match up.

Seems easier to just call this a configuration error or not if for
some reason this is really what someone intended.

.John

  reply	other threads:[~2012-07-16  4:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16  1:08 [PATCH net-next] bonding: Support for multi function NIC devices Anirban Chakraborty
2012-07-16  1:40 ` Jay Vosburgh
2012-07-16  4:39   ` John Fastabend [this message]
2012-07-16  5:12     ` Anirban Chakraborty
2012-07-16  5:50       ` Jay Vosburgh
2012-07-16  6:10         ` Anirban Chakraborty

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=50039B11.1010006@intel.com \
    --to=john.r.fastabend@intel.com \
    --cc=Dept_NX_Linux_NIC_Driver@qlogic.com \
    --cc=anirban.chakraborty@qlogic.com \
    --cc=davem@davemloft.net \
    --cc=fubar@us.ibm.com \
    --cc=netdev@vger.kernel.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