From: Andi Kleen <andi@firstfloor.org>
To: David Miller <davem@davemloft.net>
Cc: andi@firstfloor.org, shemminger@linux-foundation.org,
greearb@candelatech.com, bridge@linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] bridge: avoid ptype_all packet handling
Date: Sat, 3 Mar 2007 13:30:58 +0100 [thread overview]
Message-ID: <20070303123058.GA5357@one.firstfloor.org> (raw)
In-Reply-To: <20070302.202211.21926049.davem@davemloft.net>
On Fri, Mar 02, 2007 at 08:22:11PM -0800, David Miller wrote:
> From: Andi Kleen <andi@firstfloor.org>
> Date: 03 Mar 2007 03:14:29 +0100
>
> > That's pretty common with many x86 server boards because
> > they come with two NICs by default but must people only
> > plug the cable into one. However the distro installers
> > run DHCP on all.
>
> Nope, that's not what I've seen them do, instead they run dhcp on
> interfaces that report a link being present.
I've seen otherwise.
And that's also bad. It means that when the user moves the machine
and happens to plug the Ethernet into the other port network
will be a notwork until the configuration is manually changed.
Similar when the cable is not plugged in yet at install time.
All not good.
Allowing low overhead DHCP is useful imho. The main problem
with running it always is that it will use more power because
it will IFF_UP the interface. But longer term that can be only
properly solved by real idle network power management I think.
-Andi
next prev parent reply other threads:[~2007-03-03 12:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 1:18 [PATCH] bridge: avoid ptype_all packet handling Stephen Hemminger
2007-03-01 1:28 ` Ben Greear
2007-03-01 3:56 ` Stephen Hemminger
2007-03-01 4:05 ` Ben Greear
2007-03-01 7:04 ` Stephen Hemminger
2007-03-01 7:22 ` David Miller
2007-03-01 7:26 ` Stephen Hemminger
2007-03-01 7:30 ` David Miller
2007-03-01 11:47 ` jamal
2007-03-03 2:14 ` Andi Kleen
2007-03-03 4:22 ` David Miller
2007-03-03 7:09 ` Stephen Hemminger
2007-03-03 12:30 ` Andi Kleen [this message]
2007-03-02 21:26 ` David Miller
2007-03-02 22:09 ` [RFC 1/2] " Stephen Hemminger
2007-03-02 22:14 ` [RFC 2/2] bridge: per device promiscious taps Stephen Hemminger
2007-03-02 22:48 ` [RFC 1/2] bridge: avoid ptype_all packet handling David Miller
2007-03-02 23:18 ` David Miller
2007-03-02 23:34 ` Stephen Hemminger
2007-03-02 23:41 ` David Miller
2007-03-03 5:38 ` Herbert Xu
2007-03-03 5:59 ` David Miller
2007-03-03 6:42 ` Herbert Xu
2007-03-02 22:15 ` Stephen Hemminger
2007-03-03 12:04 ` [PATCH] " Stefan Rompf
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=20070303123058.GA5357@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=bridge@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).