From: Jay Vosburgh <fubar@us.ibm.com>
To: Pavel Simerda <psimerda@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, andy@greyhouse.net,
stephen@networkplumber.org, dcbw@redhat.com,
Jiri Pirko <jiri@resnulli.us>
Subject: Re: [patch net-next V2] bond: have random dev address by default instead of zeroes
Date: Fri, 25 Jan 2013 10:31:32 -0800 [thread overview]
Message-ID: <22106.1359138692@death.nxdomain> (raw)
In-Reply-To: <542237717.4200599.1359136587903.JavaMail.root@redhat.com>
Pavel Simerda <psimerda@redhat.com> wrote:
>----- Original Message -----
>> From: "Jay Vosburgh" <fubar@us.ibm.com>
>> but I don't think it should be changed.
>
>Just a short question. Is there any reason for bonding interfaces to
>behave differently from bridging interfaces in this respect?
To clarify, what I don't think should change is that a manually
set MAC on the bonding master should override the automatic copy of the
first slave's MAC to the bonding master. The fail_over_mac active and
follow settings are an exception to this, but those are special cases
for unusual network hardware.
As for the random MAC vs. zero MAC, I've always thought that the
all zero MAC was a clear indicator that the device (the bonding master
in this case) was not in a usable state (in the sense that it could not
send or receive actual traffic). It's not a really big deal, though, so
if the trend these days is for everything to have a MAC all the time,
that's fine, as long as doing so doesn't break anything.
I think the patch under discussion should be fine with the
addition of the last notifier call previously discussed. Some
documentation updates would be nice, too.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next prev parent reply other threads:[~2013-01-25 18:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 20:01 [patch net-next V2] bond: have random dev address by default instead of zeroes Jiri Pirko
2013-01-25 1:35 ` Jay Vosburgh
2013-01-25 6:37 ` Jiri Pirko
2013-01-25 7:22 ` Jiri Pirko
2013-01-25 17:53 ` Jay Vosburgh
2013-01-25 17:56 ` Pavel Simerda
2013-01-25 18:31 ` Jay Vosburgh [this message]
2013-01-25 19:42 ` Pavel Simerda
2013-01-25 20:00 ` Jiri Pirko
2013-01-29 17:54 ` Dan Williams
2013-01-25 18:08 ` 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=22106.1359138692@death.nxdomain \
--to=fubar@us.ibm.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=psimerda@redhat.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).