From: David Miller <davem@davemloft.net>
To: hsantos@av.it.pt
Cc: kazunori@miyazawa.org, hadi@cyberus.ca, shemminger@osdl.org,
herbert@gondor.apana.org.au, yoshfuji@linux-ipv6.org,
netdev@vger.kernel.org, usagi-core@linux-ipv6.org
Subject: Re: Regarding offloading IPv6 addrconf and ndisc
Date: Mon, 31 Jul 2006 14:23:07 -0700 (PDT) [thread overview]
Message-ID: <20060731.142307.35014994.davem@davemloft.net> (raw)
In-Reply-To: <20060730113050.GL8334@innerghost.net>
So all of you userland control-plane fanatics, how will you handle
things like NFS root with these daemon-required variants of NDISC and
ARP?
I know the devils' advocate responses already, so don't bother with
responses saying things like 1) "do it in the initial ramdisk, we only
need the daemon to setup the NDISC entries to talk to the NFS server"
or 2) "IPSEC's control plane is in userspace and therefore we can't do
NFS root over IPSEC, why is that ok and key'd NDISC is not?"
I think we are building systems which gradually are becomming less and
less reliable, with increasing numbers of possible points of failure.
Flexibility is overrated. There are many crucial optimizations and
simplifications we cannot perform because we've made certain aspects
of network configuration far too flexible.
next prev parent reply other threads:[~2006-07-31 21:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 11:25 Regarding offloading IPv6 addrconf and ndisc Hugo Santos
2006-07-27 12:25 ` Kazunori Miyazawa
2006-07-27 17:56 ` Hugo Santos
2006-07-27 23:56 ` Herbert Xu
2006-07-28 1:34 ` David Miller
2006-07-28 1:45 ` Hugo Santos
2006-07-28 2:27 ` David Miller
2006-07-28 3:13 ` Hugo Santos
2006-07-28 3:20 ` David Miller
2006-07-28 3:31 ` Hugo Santos
2006-07-28 4:07 ` Stephen Hemminger
2006-07-28 8:34 ` Hugo Santos
2006-07-28 12:45 ` Jamal Hadi Salim
2006-07-29 13:34 ` Hugo Santos
2006-07-30 3:28 ` Kazunori Miyazawa
2006-07-30 11:30 ` Hugo Santos
2006-07-31 21:23 ` David Miller [this message]
2006-08-01 11:50 ` Hugo Santos
2006-08-01 21:54 ` David Miller
2006-08-01 0:16 ` Kazunori Miyazawa
2006-07-28 2:22 ` Herbert Xu
2006-07-28 2:33 ` David Miller
2006-08-01 0:31 ` Andi Kleen
2006-08-01 0:46 ` David Miller
2006-08-01 0:49 ` Roland Dreier
2006-08-01 1:24 ` Jamal Hadi Salim
2006-08-01 1:30 ` Herbert Xu
2006-08-01 1:47 ` Jamal Hadi Salim
2006-08-01 12:13 ` Hugo Santos
2006-08-01 12:00 ` Hugo Santos
2006-08-01 21:57 ` David Miller
2006-08-03 13:28 ` Ingo Oeser
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=20060731.142307.35014994.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=herbert@gondor.apana.org.au \
--cc=hsantos@av.it.pt \
--cc=kazunori@miyazawa.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=usagi-core@linux-ipv6.org \
--cc=yoshfuji@linux-ipv6.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).