Netdev List
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz@voltaire.com>
To: netdev@vger.kernel.org
Cc: rdreier@cisco.com
Subject: bonding questions: carrier based link monitoring / slave device state flags
Date: Thu, 3 Aug 2006 08:59:31 +0300 (IDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0608030815270.32510@zuben> (raw)

First, i'd like to verify what is the parameter setting to have the
bonding driver use netif_carrier_ok(slave_device) as the means for
link detection. Is setting use_carrier = 1 enough or one needs to set
miimon to non-zero as well??? (where the value of miimon translates
to the link monitoring frequency).

Second, I understand that an enslaved device must **not** be UP, so
when enslaving a device the bonding driver calls dev_open(slave_device),
and make sure the device is UP, correct?

What i want to better understand here, is whether for the bonding driver
to declare a slave as "being able to carry traffic" it assumes the slave
will move from UP to RUNNING state (and later netif_carrier_ok would
return TRUE) without an IP address being set for the slave device ???

Is (per the bonding driver) the **time** it should take the slave to get
from UP to (RUNNING && carrier_ok) state limited and/or controlled?

Or.


             reply	other threads:[~2006-08-03  5:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03  5:59 Or Gerlitz [this message]
2006-08-04  0:19 ` bonding questions: carrier based link monitoring / slave device state flags Jay Vosburgh
2006-08-08 13:24   ` Or Gerlitz
2006-08-08 14:05 ` bonding questions: "replaying" call to set_multicast_list and sending IGMP doing Fail-Over Or Gerlitz
2006-08-08 17:20   ` Jay Vosburgh
2006-08-10 13:03     ` Or Gerlitz

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=Pine.LNX.4.64.0608030815270.32510@zuben \
    --to=ogerlitz@voltaire.com \
    --cc=netdev@vger.kernel.org \
    --cc=rdreier@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox