All of lore.kernel.org
 help / color / mirror / Atom feed
From: Poornima Kamath <poornimak@gslab.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: netdev@vger.kernel.org
Subject: Re: Detecting backup slaves of bonding interface in network driver
Date: Mon, 29 Dec 2008 15:58:49 +0530	[thread overview]
Message-ID: <4958A661.9020601@gslab.com> (raw)
In-Reply-To: <3481.1229099865@death.nxdomain.ibm.com>

Hi Jay,

 Thanks a lot for your  response.
 ib-bonding does have  fail_over_mac functionality and works on both 
RHEL5 and SLES10.

Thanks,
Poornima

Jay Vosburgh wrote:
> Poornima Kamath <poornimak@gslab.com> wrote:
>
>   
>> The driver creates virtual interfaces that talk to ethernet interfaces over
>> infiniband,  using an infiniband to ethernet gateway device.
>> The gateway device sends data to all interfaces having same mac address.  For
>> this the driver needs to explicitly tell the gateway device not to send data to
>> the backup slaves.
>> Therefore the driver needs to  know which slaves are backup slaves.
>> The failover mac option  works well,  but it is present for kernels greater
>> than 2.6.24.  So this option is not available for distros like RHEL5, SLES10
>> etc
>>     
>
> 	I believe that RHEL5 and SLES10 contain an "ib-bonding" package
> which includes a backport of the current (or at least a more current)
> bonding driver specifically for use over Infiniband.  I think it's also
> got a couple of other patches to bonding that aren't in the mainline.
> In any event, it has the fail_over_mac functionality.
>
> 	Have you looked at ib-bonding?
>
>   
>> So in order to support these distros I need some way of identifying the backup
>> slaves.
>> Is it ok to check the IFF_SLAVE_INACTIVE flags for these distros?
>>     
>
> 	It will do what you want (identify backup slaves), and is not
> guaranteed to be available in the future.  I doubt that the flag would
> ever go away on RHEL5 or SLES10, but, again, no guarantee.
>
> 	-J
>
> ---
> 	-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>   


  reply	other threads:[~2008-12-29 10:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 12:34 Detecting backup slaves of bonding interface in network driver Poornima Kamath
2008-12-11 16:35 ` Jay Vosburgh
     [not found]   ` <4942663A.3080801@gslab.com>
2008-12-12 16:37     ` Jay Vosburgh
2008-12-29 10:28       ` Poornima Kamath [this message]
2008-12-15  5:08   ` Poornima Kamath

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=4958A661.9020601@gslab.com \
    --to=poornimak@gslab.com \
    --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 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.