From: David Miller <davem@redhat.com>
To: netdev@vger.kernel.org
Cc: shemminger@vyatta.com
Subject: bridge carrier issue
Date: Tue, 20 Sep 2011 15:29:53 -0400 (EDT) [thread overview]
Message-ID: <20110920.152953.448244771460257273.davem@redhat.com> (raw)
I'm marking the patches in patchwork on this as "deferred".
It is my opinion that we need to push back on the virtualization stuff
because otherwise it is impossible for network manager and friends to
operate properly.
Without the carrier going on only when a device is actually attached
and operating, NM has no "signal" to know when it actually should do
DHCP and whatnot.
On the other hand, the virtualization tools and libraries can operate
properly within the constraints added by the carrier behavior we have
now.
And I also believe they can do so in a way that allows them to work
on kernels before the carrier change.
Therefore, the only way to move forward and get everything working is
to change the virtualization tools.
next reply other threads:[~2011-09-20 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 19:29 David Miller [this message]
2011-09-20 21:12 ` bridge carrier issue Dan Williams
2011-09-20 23:00 ` Stephen Hemminger
2011-09-25 8:51 ` Marc Haber
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=20110920.152953.448244771460257273.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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